Bug 1901572
Summary: | RHV-M doesn't display guest information of HostedEngine VM | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Juan Orti <jortialc> | ||||||||||
Component: | ovirt-engine | Assignee: | Arik <ahadas> | ||||||||||
Status: | CLOSED ERRATA | QA Contact: | Nikolai Sednev <nsednev> | ||||||||||
Severity: | low | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 4.2.7 | CC: | ahadas, ddacosta, dfodor, mavital, michal.skrivanek, nsednev, sbonazzo, tgolembi | ||||||||||
Target Milestone: | ovirt-4.4.8 | Keywords: | Triaged | ||||||||||
Target Release: | --- | ||||||||||||
Hardware: | Unspecified | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | ovirt-engine-4.4.8.3 | Doc Type: | If docs needed, set a value | ||||||||||
Doc Text: |
Previously, there was a race condition that prevented RHV-M from displaying the guest agent information of the HostedEngine virutal machine. The current release fixes this issue and the information displays correctly in the Administration Portal.
|
Story Points: | --- | ||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2021-09-08 14:12:04 UTC | Type: | Bug | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | --- | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Attachments: |
|
Description
Juan Orti
2020-11-25 15:02:42 UTC
(In reply to Juan Orti Alcaine from comment #0) > Version-Release number of selected component (if applicable): > ovirt-engine-4.2.7.4-0.1.el7ev.noarch Please upgrade the manager to the current GA version, 4.4. Other than that, this shouldn't be blocking, right? It's supposedly the IP you're using to access the portal in a first place. Does this still reproduce in 4.4? Doesn't reproduced on rhvm-4.4.4.2-0.1.el8ev.noarch. (In reply to Nikolai Sednev from comment #6) > Doesn't reproduced on rhvm-4.4.4.2-0.1.el8ev.noarch. Double checked now on fresh and latest version:4.4.3.12-0.1.el8ev and IP address is not reported for the engine VM. Screenshot is attached. Created attachment 1736973 [details]
Screenshot from 2020-12-06 16-38-45.png
I used the qemu-guest-agent-4.2.0-34.module+el8.3.0+7976+077be4ec.x86_64 on the engine. Nikolai, Please try with downgrading to http://pulp-read.dist.prod.ext.phx2.redhat.com/content/dist/rhel8/8/x86_64/appstream/os/Packages/q/qemu-kvm-2.12.0-99.module+el8.2.0+7988+c1d02dbb.4.x86_64.rpm alma03 ~]# yum downgrade -y http://pulp-read.dist.prod.ext.phx2.redhat.com/content/dist/rhel8/8/x86_64/appstream/os/Packages/q/qemu-kvm-2.12.0-99.module+el8.2.0+7988+c1d02dbb.4.x86_64.rpm Updating Subscription Management repositories. Unable to read consumer identity This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. Last metadata expiration check: 0:05:12 ago on Mon 14 Dec 2020 11:45:09 AM IST. qemu-kvm-2.12.0-99.module+el8.2.0+7988+c1d02dbb.4.x86_64.rpm 122 kB/s | 102 kB 00:00 Error: Problem: conflicting requests - nothing provides qemu-kvm-block-curl = 15:2.12.0-99.module+el8.2.0+7988+c1d02dbb.4 needed by qemu-kvm-15:2.12.0-99.module+el8.2.0+7988+c1d02dbb.4.x86_64 - nothing provides qemu-kvm-block-gluster = 15:2.12.0-99.module+el8.2.0+7988+c1d02dbb.4 needed by qemu-kvm-15:2.12.0-99.module+el8.2.0+7988+c1d02dbb.4.x86_64 - nothing provides qemu-kvm-block-iscsi = 15:2.12.0-99.module+el8.2.0+7988+c1d02dbb.4 needed by qemu-kvm-15:2.12.0-99.module+el8.2.0+7988+c1d02dbb.4.x86_64 - nothing provides qemu-kvm-block-rbd = 15:2.12.0-99.module+el8.2.0+7988+c1d02dbb.4 needed by qemu-kvm-15:2.12.0-99.module+el8.2.0+7988+c1d02dbb.4.x86_64 - nothing provides qemu-kvm-block-ssh = 15:2.12.0-99.module+el8.2.0+7988+c1d02dbb.4 needed by qemu-kvm-15:2.12.0-99.module+el8.2.0+7988+c1d02dbb.4.x86_64 - nothing provides qemu-kvm-core = 15:2.12.0-99.module+el8.2.0+7988+c1d02dbb.4 needed by qemu-kvm-15:2.12.0-99.module+el8.2.0+7988+c1d02dbb.4.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Created attachment 1743449 [details]
HE444Screenshot
Looks ok with RHV-M 4.4.4.6
Not working on these components: rhvm-4.4.4.6-0.1.el8ev.noarch qemu-guest-agent-4.2.0-34.module+el8.3.0+9094+80c20d97.2.x86_64 Screenshot attached. Created attachment 1743454 [details]
Screenshot from 2020-12-31 18-01-00.png
what do you get with: select vm_ip from vms where vm_name='HostedEngine'; when the IP is not shown? if that returns an empty string, does it change by executing: update vm_dynamic set guest_agent_nics_hash = NULL where vm_guid in (select vm_guid from vm_static where vm_name='HostedEngine'); ? engine=# select vm_ip from vms where vm_name='HostedEngine'; vm_ip ------- (1 row) engine-# update vm_dynamic set guest_agent_nics_hash = NULL where vm_guid in (select vm_guid from vm_static where vm_name='HostedEngine'); ERROR: syntax error at or near "vm_ip" LINE 1: vm_ip ^ engine=# I just reran it again now and got these: nsednev-he-1 ~]# su - postgres -c psql psql (12.5) Type "help" for help. postgres=# \c engine You are now connected to database "engine" as user "postgres". engine=# select vm_ip from vms where vm_name='HostedEngine'; vm_ip ------------------------------------------------------------------------ 10.35.92.51 2620:52:0:235c:216:3eff:fe7b:b853 fe80::216:3eff:fe7b:b853 (1 row) engine=# update vm_dynamic set guest_agent_nics_hash = NULL where vm_guid in (select vm_guid from vm_static where vm_name='HostedEngine'); UPDATE 1 engine=# For some reason the engine now is reporting the IP as appears in the attachment. Created attachment 1745971 [details]
Screenshot from 2021-01-10 11-19-52.png
Looks like "update vm_dynamic set guest_agent_nics_hash = NULL where vm_guid in (select vm_guid from vm_static where vm_name='HostedEngine');" has triggered the change. Thanks Nikolai So it appears like we have some kind of race or we don't clear the guest_agent_nics_hash field in some cases (In reply to Arik from comment #21) > So it appears like we have some kind of race or we don't clear the guest_agent_nics_hash field in some cases Actually looking again at comment 18, I see that vm_ip was set in the database before the hash was cleared so clearing the hash had no impact in this case - what is displayed in the screenshot attached in comment 19 must have been displayed also right before the hash was cleared I suspected that it's the same as bz 1981946 where the hosted engine VM is also mentioned but I managed to reproduce the scenario described in comment 0 in which the NICs are set with IP address(es) and vm_ip is not displayed: 1. the hosted engine VM is stopped on a first host and moves to Down state 2. the agent starts the hosted engine VM on a second host 3. ovirt-engine detects the VM as Down on the first host and calls 'destroy' + set the VM with Down state in the database which means vm_ip + guest_agent_nics_hash also get cleared 4. ovirt-engine detects the VM "unexpectedly" on the second host and therefore saves it in the database with the new guest_agent_nics_hash and without updating vm_ip 5. as a result, the information from the guest agent on the NICs exists but vm_ip is never set as the reported hash never changes again Version 4.4.8.3-0.10.el8ev works fine. 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 (RHV Manager (ovirt-engine) [ovirt-4.4.8]), 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/RHBA-2021:3460 Due to QE capacity we are not going to cover this issue in our automation |