+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1703428 +++ ====================================================================== Description of problem: VMs migrated from KVM to RHV show the warning 'The latest guest agent needs to be installed and running on the guest'. The guest has ovirt-guest-agent-common and qemu-guest-agent installed: ~~~~~~~ ovirt-guest-agent-common-1.0.14-1.el7.noarch qemu-guest-agent-2.12.0-2.el7.x86_64 ~~~~~~ Also, the services are running on the VM: ~~~~~~ * ovirt-guest-agent.service - oVirt Guest Agent Loaded: loaded (/usr/lib/systemd/system/ovirt-guest-agent.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2019-04-22 11:09:27 CDT; 20h ago Process: 2799 ExecStartPre=/bin/chown ovirtagent:ovirtagent /run/ovirt-guest-agent.pid (code=exited, status=0/SUCCESS) Process: 2766 ExecStartPre=/bin/touch /run/ovirt-guest-agent.pid (code=exited, status=0/SUCCESS) Process: 2749 ExecStartPre=/sbin/modprobe virtio_console (code=exited, status=0/SUCCESS) * qemu-guest-agent.service - QEMU Guest Agent Loaded: loaded (/usr/lib/systemd/system/qemu-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2019-04-22 11:09:27 CDT; 20h ago Main PID: 2747 (qemu-ga) CGroup: /system.slice/qemu-guest-agent.service `-2747 /usr/bin/qemu-ga --method=virtio-serial --path=/dev/virtio-ports/org.qemu.guest_agent.0 --blacklist=guest-file-open,guest-file-close,guest-file-read,guest-file-write,guest-file-seek,guest-file-flush,guest-exec,guest-exec-status -F/etc/qemu-ga/fsfreeze-hook ~~~~~~ Version-Release number of selected component (if applicable): ovirt-guest-agent-common-1.0.14-1.el7.noarch qemu-guest-agent-2.12.0-2.el7.x86_64 Actual results: VMs show the warning 'The latest guest agent needs to be installed and running on the guest' on RHV portal. Expected results: VMs should not show the warning 'The latest guest agent needs to be installed and running on the guest' on RHV portal if the guest-agent is installed on it. (Originally by Abhishekh Patil)
Please provide information from the 'Guest Agent info' tab for this VM. (Originally by Tomas Golembiovsky)
Hi Tomáš. Abhishekh opened this bug on my behalf. So, I'll chime in. By "Guest Agent info" tab for this VM, I assume you mean the "Guest Info" tab for the VM under Compute->Virtual Machines in the RHEV-M gui. If so, here you go: Type: Linux Timezone: America/Chicago (UTC--06:-00) Logged-in User: None Architecture: x86_64 Console User: Operating System: Red Hat Enterprise Linux Server 7.6 (Maipo) Console Client IP: Kernel Version: 3.10.0-957.10.1.el7.x86_64 (Originally by bwalton)
what's the OS Type set for that VM? (Originally by michal.skrivanek)
the alert if always going to be there for Other OS, see https://github.com/oVirt/ovirt-engine/blob/8d35e763e90f943c8d0a5c677a8b796d4c6f39d3/frontend/webadmin/modules/webadmin/src/main/java/org/ovirt/engine/ui/webadmin/widget/table/column/VmStatusIconColumn.java#L113 (Originally by michal.skrivanek)
When I imported the VM from our KVM installation, I chose "Red Hat Enterprise Linux 7.x x64" in the Operating System field. If there is some other place you would like me to look for this setting, please let me know. (Originally by bwalton)
Also, output from: [root@rhevm bwalton]# /usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "select vm_name,guestos_type from vms where vm_name='migratetest';" vm_name | guestos_type -------------+-------------- migratetest | Linux (1 row) [root@rhevm bwalton]# (Originally by bwalton)
I think it checks OS version reported by guest agent, not from VM options. And based on comment #3 it looks OK to me. In logs I see the ovirt-engine version is 4.2.8.3-0.1.el7ev Shmuel, any ideas? (Originally by Tomas Golembiovsky)
I'm puzzled by that as well, the "guestAgentNotAvailable" message is only displayed when the guest agent is not detected (VM is Up and hasGuestAgent(vm) returns false) which has this condition: vm.getTimeZone() != null && vm.getGuestOsType() != null && vm.getGuestOsType() != OsType.Other; clearly TZ is reported and OS is not Other. Can you doublecheck/paste the whole row in "vms" table for this VM please? You can add that as a private comment. (Originally by michal.skrivanek)
Still it looks like a frontend issue only, the agent is apparently running and reporting all the info so from that perspective all the functionality should be ok (Originally by michal.skrivanek)
It may that there is some internal inconsistency about the timezone info - the zone info in Guest Info tab comes from vm.getGuestOsTimezoneName() - but the check is performed against vm.getTimeZone() (which despite the name is also from guest info) Just for the record, you could you please run: vdsm-client Host getAllVmStats What is the content of `guestTimezone` structure? (Originally by Tomas Golembiovsky)
Tomáš, when I run "vdsm-client Host getAllVmStats" on the hypervisor, the output for guestTimezone shows: "guestTimezone": { "zone": "America/Chicago", "offset": -360 }, Michal, I apologize, but would you please tell me how/where to find the "vms" table for the VM? Thanks! (Originally by bwalton)
Tomas, Shmuel: Same value is in the database for this vm: guest_timezone_offset | -360 guest_timezone_name | America/Chicago Can you please check next steps? (Originally by Marina Kalinin)
sync2jira
Verification builds: ovirt-engine-4.3.7.0-0.1.el7 vdsm-4.30.30-1.el7ev.x86_64 qemu-kvm-rhev-2.12.0-33.el7_7.3.x86_64 libvirt-4.5.0-23.el7_7.1.x86_64 Verification scenario: 1. Prepare the next VMs on KVM server: - RHEL 7 VM without ovirt and qemu guest agents and EDT hwclock - RHEL 7 VM with ovirt and qemu guest agents and EDT hwclock (ovirt host hwclock is IST, so it's an offset of -6 hours) 2. From RHV WebAdmin, import both VMs and run them. 3. On the VM with guest agent, verify services are up and guest agent is in sync with the host. 4. Observe VMs warning messages on WebAdmin -> virtual machines view: - No message should be observed on the VM with guest agents. - 'The latest guest agent needs to be installed and running on the guest' warning message should be on the VM without guest agents. Screenshot example attached (GA_warning.png)
Created attachment 1630436 [details] GA_warning.png
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/RHBA-2019:4229