Bug 1703428
Summary: | VMs migrated from KVM to RHV show warning 'The latest guest agent needs to be installed and running on the guest' | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Abhishekh Patil <abpatil> | |
Component: | ovirt-engine | Assignee: | Liran Rotenberg <lrotenbe> | |
Status: | CLOSED ERRATA | QA Contact: | Nisim Simsolo <nsimsolo> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 4.2.8 | CC: | achareka, adevolder, ahadas, bwalton, emarcus, lrotenbe, lsurette, lsvaty, michal.skrivanek, mkalinin, mkenneth, mtessun, nsimsolo, smelamud, srevivo, tgolembi | |
Target Milestone: | ovirt-4.4.1 | Keywords: | Triaged, ZStream | |
Target Release: | --- | Flags: | lsvaty:
testing_plan_complete-
|
|
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Previously, when importing a KVM into Red Hat Virtualization, "Hardware Clock Time Offset" was not set. As a result, the Manager machine did not recognize the guest agent installed in the virtual machine.
In this release, the Manager machine recognizes the guest agent on a virtual machine imported from KVM, and the "Hardware Clock Time Offset" won't be null.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1743427 (view as bug list) | Environment: | ||
Last Closed: | 2020-08-04 13:19:21 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1743427 |
Description
Abhishekh Patil
2019-04-26 11:55:12 UTC
Please provide information from the 'Guest Agent info' tab for this VM. 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 what's the OS Type set for that VM? 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 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. 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]# 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? 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. 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 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? 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! 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? sync2jira sync2jira WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops Verified: rhvm-4.4.0-0.9.master.el7 vdsm-4.40.0-164.git38a19bb.el8ev.x86_64 qemu-kvm-4.1.0-10.module+el8.1.0+4234+33aa4f57.x86_64 libvirt-5.6.0-5.module+el8.1.0+4229+2e4e348c.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. WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops 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 (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), 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-2020:3247 |