New commit detected on ManageIQ/manageiq/fine: https://github.com/ManageIQ/manageiq/commit/1bc69271362db8aa0ea220c5842d4f8e9f0ec054 commit 1bc69271362db8aa0ea220c5842d4f8e9f0ec054 Author: Adam Grare <agrare> AuthorDate: Wed Apr 12 07:54:05 2017 -0400 Commit: Satoe Imaishi <simaishi> CommitDate: Thu Apr 13 14:43:38 2017 -0400 Merge pull request #14741 from Ladas/ensure_managers_change_zone_and_provider_region_with_cloud_manager Method for ensuring managers change zone and provider region with CloudManager (cherry picked from commit 9cae7823ad1538f281e74235c41b891cfcae45aa) https://bugzilla.redhat.com/show_bug.cgi?id=1441740 https://bugzilla.redhat.com/show_bug.cgi?id=1441753 app/models/mixins/has_network_manager_mixin.rb | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-)
New commit detected on ManageIQ/manageiq-providers-azure/fine: https://github.com/ManageIQ/manageiq-providers-azure/commit/1d98337e7042169402804fcf2c206f17975979c3 commit 1d98337e7042169402804fcf2c206f17975979c3 Author: Bronagh Sorota <bsorota> AuthorDate: Wed Apr 12 11:16:05 2017 -0400 Commit: Satoe Imaishi <simaishi> CommitDate: Thu Apr 13 15:15:33 2017 -0400 Merge pull request #47 from Ladas/ensure_managers_change_zone_and_provider_region_with_cloud_manager Ensure managers change zone and provider region with CloudManager (cherry picked from commit 76299c0ddc050e5ea40dcaf91b278ac105811260) https://bugzilla.redhat.com/show_bug.cgi?id=1441753 app/models/manageiq/providers/azure/cloud_manager.rb | 1 + .../manageiq/providers/azure/cloud_manager_spec.rb | 19 +++++++++++++++++++ 2 files changed, 20 insertions(+)
I'll check this one out in the morning.
This is working fine for me. Keep in mind that DHCP Ip addresses are only available if the VM is running and the IP is a Public IP address. Here is my example output: Name cfme-azure-58012 IP Addresses 10.1.0.4, 52.167.135.31 MAC Address 00-0D-3A-02-9B-21 Container Show VMM container information azure: 4 CPUs (1 socket x 0 cores), 7168 MB
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. https://access.redhat.com/errata/RHSA-2017:1367