Created attachment 1200624 [details]
vm details screenshot
Description of problem:
Investigating IPv6 support, John asked and we confirmed that IPv6 addresses are not shown on the details page. Some good news, they are there, you have to click on the field which pushes you to a network adapter page where it does show the ipv6 address. Not sure how serious this is, ultimately its not ideal if working in a straight IPv6 network and it might be better to make it configurable as to what address is shown?
See the screenshots.
Version-Release number of selected component (if applicable):
The Vm.ipaddresses list gets populated from Hardware/Network association.
I have been looking into where we use ipaddresses internally if we can include ipv6 in the list as well. We use the Vm.ipaddresses not only for presentation, but also for things like cockpit window or automate tasks. Our internal use shouldn't broke if we include ipv6 in Vm.ipaddress. It may actually help in cases of ipv6 only connectivity.
Question is, do we ever need to keep these separated?
New commit detected on ManageIQ/manageiq/master:
Author: James Wong <email@example.com>
AuthorDate: Wed Dec 14 23:41:49 2016 -0500
Commit: James Wong <firstname.lastname@example.org>
CommitDate: Wed Dec 14 23:42:11 2016 -0500
display IPv6Address on VM summary page
app/models/hardware.rb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Verified in CFME 188.8.131.52-alpha1
The VM summary page shows configured IPv6 addresses in the 'IP Addresses' field under the 'Properties' table, comma separated in the case where more than one IPv6 address is detected on the server.
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.