Red Hat Bugzilla – Bug 1375737
IPv6 addresses not rendered on details page
Last modified: 2017-05-31 10:21:18 EDT
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): ============================ 5.6.1.2
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?
https://github.com/ManageIQ/manageiq/pull/13190
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/e46e282988de9b00685bf3915baf127064cf6884 commit e46e282988de9b00685bf3915baf127064cf6884 Author: James Wong <jwong@redhat.com> AuthorDate: Wed Dec 14 23:41:49 2016 -0500 Commit: James Wong <jwong@redhat.com> CommitDate: Wed Dec 14 23:42:11 2016 -0500 display IPv6Address on VM summary page https://bugzilla.redhat.com/show_bug.cgi?id=1375737 app/models/hardware.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Verified in CFME 5.8.0.8-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. https://access.redhat.com/errata/RHSA-2017:1367