engine.log gets flooded with 'Invalid or unknown guest architecture type'
Environment
- Red Hat Enterprise Virtualization 3.x, 4.x
- Red Hat Enterprise Linux 5 Guest
- rhevm-guest-agent
- 32-bits architecture
Issue
- Installing/enabling rhevm-guest-agent service in RHEL 5 guests with arch of 32-bits will make guest-agent to report arch type as i386, i486, i586 or i686 which isn't translated to x86 which is what engine understands.
- engine.log will flood with warning messages like:
WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (DefaultQuartzScheduler_Worker-55) [269a6eee] Invalid or unknown guest architecture type 'i686' received from guest agent
Resolution
Fixed in 1332723, please upgrade to rhevm-guest-agent-1.0.12-3.el5ev version to fix the issue.
As a workaround one could stop/disable the service from RHEL 5 32-bits architecture based guests to avoid flooding engine.log with warning messages.
Root Cause
- The Guest agent wasn't translating x86 architecture strings like i386, i486, i586, i686 to string 'x86' which is the only type the engine understands.
- Every time the engine retrieved an update from the Hypervisors which had hosts like this, the exceptions were thrown.
- With this update the x86 architectures are now correctly translated and no more flooding to engine.log happens.
Diagnostic Steps
-
Run the ovirt-osinfo in the guest and check for results:
# /usr/share/ovirt-guest-agent/ovirt-osinfo distribution=Red Hat Enterprise Linux Server version=5.11 codename=Tikanga arch=i686 <========= This should be x86 instead kernel=2.6.18-409.el5 type=linux
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
