Created attachment 1248404 [details]
ipv6 address missing in 'IP Address' column
Description of problem:
When there are v6 IPs only, 'IP Address' column shows no IP address at all. It seems 'IP Address' column is IPv4-only.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Windows VM with ovirt-guest-agent
2. Have only IPv6 enabled inside VM network settings
3. check reported data for the VM in Network subtab
4. check if there is any IP in 'IP Address' column in VM main tab for the VM
no IP at all
IPv6 address should be visible
thus columnt should probably be renamed to 'IP Addresses' and should display both v4 and v6 IPs.
Sorry for the late response, but can you help us understand where is the bug (ovirt-engine, vdsm or ovirt-guest-agent)
Is the IPv6-only address reported in guestIPs by
`vdsm-client Host getAllVmStats` ?
(In reply to Dan Kenigsberg from comment #1)
> Sorry for the late response, but can you help us understand where is the bug
> (ovirt-engine, vdsm or ovirt-guest-agent)
> Is the IPv6-only address reported in guestIPs by
> `vdsm-client Host getAllVmStats` ?
It seems to be engine/wedadmin issue as two IPv6 addresses are visible in the right bottom part of the screenshot - those are IPs reported by GA and we visible in getVmStats $vmid.
I suppose 'IP Address' column in Admin Portal which should display IPs handles only IPv4. Thus I would recommend to check this first.
Testing this on 4.2.0-0.0.master.20171029154613.git19686f3.el7.centos give me some weird results.
IPv6 doesn't shows in the IP addr column, only IPv4. In some attempts it showed the IPv6 for a second and then it's gone again.
Burman, can you share what vdsm reports vs what is shown in UI and over REST?
(In reply to Dan Kenigsberg from comment #4)
> Burman, can you share what vdsm reports vs what is shown in UI and over REST?
REST - Report's the IPv6 addresses -
UI - In the IP address column i see only IPv4 address and under the VM's Guest agent sub tab i see both IPv4 and IPv6(as always was)
root@camel-vdsa ~]# vdsm-client VM getStats vmID='534063f0-ec2a-4232-84b1-5b2c82868225' | grep netIfaces -A 10
strange, i saw ipv6 link address for a "while" and then it disappeared from web ui - ovirt-engine-webadmin-portal-4.2.0-0.0.master.20171029154613.git19686f3.el7.centos.noarch
Yeah. It is weird. I'll have to investigate it further. Till then moving to MODFIED.
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:
[No relevant external trackers attached]
For more info please contact: firstname.lastname@example.org
seems like moved back to ON_QA by mistake.
Yes, it was moved automatically.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Please retest, now that bug 1512572 is fixed.
(In reply to Dan Kenigsberg from comment #12)
> Please retest, now that bug 1512572 is fixed.
Dan, this bug shouldn't be ON_QA.
Jiri Hi, i'm not sure if you already tested this report after Dan moved it again to ON_QA, but it wasn't fixed. The IPV6 address still appear for few seconds and then it's gone. Relevant for - 4.2.0-0.0.master.20171127212333.git11e14b9.el7.centos
based on #13 (i haven't test that personally.)
Actually, it is not yet merged to the stable ovirt-engine-4.2 branch.
Same thing on 4.2.2-0.1.el7
IPv6 addresses got disappeared after few seconds. Only ipv4 remain in the column.
Only now, on the new d/s build this is really fixed. 126.96.36.199-0.1.el7 seems to be fine now.
ok, ovirt-engine-webadmin-portal-188.8.131.52-0.1.el7.noarch, ovirt-engine-webadmin-portal-184.108.40.206-0.1.el7.noarch
Guest Agent Data:
IPv6 fe80::21a:4aff:fe01:3f22, 2620:52:0:2588:21a:4aff:fe01:3f22
Admin portal (Vms):
jbelka-kickstarttest | | slot-6b | fe80::21a:4aff:fe01:3f22 2620:52:0:2588:21a:4aff:fe01:3f22 | ...
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.
Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.