-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure Discover process is failing with the below error "undefined method `address_prefix' for #<Azure::Armrest::Network::VirtualNetwork::Properties::Subnet::Properties:0x000..." #547
Comments
@prasadanvekar the "fix" can be relatively easy but I'd like to see what these subnets look like since a subnet without an addressPrefix isn't very helpful and I'm wondering if maybe there is some other option we need to look at. Could you apply the following patch on your appliance and restart it, then get the logging output?
|
@agrare Thanks for sharing the patch. I can see the error is not being displayed now and discovery process is able to collect all the resource details. |
Thanks for getting this so quickly @prasadanvekar! It looks like the journal output is being chopped off, could you redirect the output to a file like |
output.log |
Thanks @prasadanvekar so there is a single subnet that doesn't have an addressPrefix, |
@agrare i can see the addressPrefix 172...*/24 available for cxf-az-network-subnet1 in Azure. The only difference i can spot is it is connected to a NAT gateway. |
Okay great let me see about replicating that in our azure environment |
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on |
Azure discover process is failing to retrieve all the resources as the process failing with
"undefined method 'address_prefix' for #<Azure::Armrest::Network::VirtualNetwork::Properties::Subnet::Properties:0x000..."
-- Impacts all versions. Have tested on Najdorf, Oparin and Petrosian.
The text was updated successfully, but these errors were encountered: