Red Hat Bugzilla – Bug 1316026
Unable to list multiple IP Addresses of an instance running on OpenStack environment.
Last modified: 2017-08-29 23:49:49 EDT
Description of problem:
Unable to list multiple IP Addresses of a virtual machine in Openstack environment.
Virtual machine in OpenStack environment has got two NIC's associated of same network and different subnets. When we try to list details of this virtual machine via CFME REST API, it lists only one IP Address.
Even from CFME console , it shows only one IP Address associated with that VM.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Launce an instance with two nics on OpenStack environment
2. Then refresh OpenStack provider from CloudForms UI.
3. New instance will be discovered.
It is showing only one IP address on CFME UI.
Ideally, it should display all the IP addresses of VM associated with it.
Also we have checked it with the GET API call and it is showing only one IP:
this BZ should be fixed by fixing https://bugzilla.redhat.com/show_bug.cgi?id=1303997
New commit detected on ManageIQ/manageiq/master:
Author: Ladislav Smola <email@example.com>
AuthorDate: Wed May 4 14:55:54 2016 +0200
Commit: Ladislav Smola <firstname.lastname@example.org>
CommitDate: Fri May 6 14:45:14 2016 +0200
For Cloud VMs show IPs and MACs based on network_ports
For Cloud VMs show IPs and MACs based on network_ports. Which is
also fixing showing ip's when VM have multiple ports. And for
ipv6, showing all IPs, even when multiple IPs are associated to
For now, only Google Provider is not supporting this, until it will
be rewritten to use a NetworkManager.
app/models/manageiq/providers/cloud_manager/vm.rb | 11 +++++++++++
app/models/manageiq/providers/google/cloud_manager/vm.rb | 11 +++++++++++
app/models/network_port.rb | 16 ++++++++++++++++
3 files changed, 38 insertions(+)
Verified in: 220.127.116.11-rc1-nightly.20160527091122_ced67ee
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.