Red Hat Bugzilla – Bug 1468700
Azure refresh fails with private_ip_address property not found
Last modified: 2017-09-21 10:24:47 EDT
New commit detected on ManageIQ/manageiq-providers-azure/fine:
Author: Bronagh Sorota <firstname.lastname@example.org>
AuthorDate: Tue Jun 27 09:38:26 2017 -0400
Commit: Satoe Imaishi <email@example.com>
CommitDate: Fri Jul 7 12:49:33 2017 -0400
Merge pull request #85 from djberg96/private_ip
Handle possibility of network_port not having private_ip_address
(cherry picked from commit cb44c138c3496d5cc7326dc4df923c10969e170e)
app/models/manageiq/providers/azure/network_manager/refresh_parser.rb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Can you answer Leo's question?
You automatically get a 10.x.x.x ip address (or however you define your sub) when you create a VM whether you ask for it or not. You have to connect somehow. Is the bug that it's not showing up in the IP list.
Just picking a VM at random, it is showing the private IP address -
PUBLIC IP ADDRESS/DNS NAME LABEL
PRIVATE IP ADDRESS
IP Addresses 10.3.0.4, 184.108.40.206
Looks fine to me.
It is possible to add an IPV6 to a load balancer for internal communication. I'll have to take a look. I'm still not aware of how to assign an IPV6 to a VM directly but that doesn't mean something hasn't changed recently.
Took a half a day but I think I figured it out. The only way to get an IPV6 attached to a VM is to spin up an entire Load Balancer. I'll paste the code under a separate pastebin or equivelent.
[----] E, [2017-07-25T17:05:11.235152 #21461:79b134] ERROR -- : MIQ(MiqQueue#deliver) Message id: , Error: [undefined method `subnet' for #<Azure::Armrest::Network::NetworkInterface::Properties::IpConfiguration::Properties:0x0000000a025be8>]
[----] E, [2017-07-25T17:05:11.235323 #21461:79b134] ERROR -- : [EmsRefresh::Refreshers::EmsRefresherMixin::PartialRefreshError]: undefined method `subnet' for #<Azure::Armrest::Network::NetworkInterface::Properties::IpConfiguration::Properties:0x0000000a025be8> Method:[rescue in deliver]
Are you in a position to test this now that Jeff has provided steps to reproduce this?
Here's a script to create what you need, but it's already been run. Just add the standard azure provider and check the evm.log until the error goes away.
You'll see the whole shebang in a resource group called LBIP4IP6. Just turn the two VMs on and refresh cfme after they are running.
Bronagh, it's reproducible
As Jeff wrote - now we have:
E, [2017-08-01T03:47:36.722872 #32376:98713c] ERROR -- : MIQ(ManageIQ::Providers::Azure::NetworkManager::Refresher#refresh) EMS: [azure Network Manager], id:  Refresh failed
[----] E, [2017-08-01T03:47:36.728311 #32376:98713c] ERROR -- : [NoMethodError]: undefined method `subnet' for #<Azure::Armrest::Network::NetworkInterface::Properties::IpConfiguration::Properties:0x000000124bf480> Method:[rescue in block in refresh]
[----] E, [2017-08-01T03:47:36.728455 #32376:98713c] ERROR -- : /opt/rh/cfme-gemset/bundler/gems/manageiq-providers-azure-ae2e0e06ee85/app/models/manageiq/providers/azure/network_manager/refresh_parser.rb:394:in `parse_cloud_subnet_network_port'
It is based on IPV6 IP Configuration without Private IP address assigned to VM/Nic
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.