Bug 1460863 - AgentAppName doesn't match latest guest agent.
AgentAppName doesn't match latest guest agent.
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhevm-setup-plugins (Show other bugs)
x86_64 Linux
high Severity high
: ovirt-4.2.0
: ---
Assigned To: Petr Kotas
Petr Matyáš
: ZStream
Depends On:
Blocks: 1464339
  Show dependency treegraph
Reported: 2017-06-12 21:46 EDT by Germano Veit Michel
Modified: 2017-11-06 10:35 EST (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The guest agent was renamed from rhev-guest-agent to ovirt-guest-agent and the guest agent check did not account for this change. Consequence: Users cannot install guest agent properly. They new they need ovirt-guest-agent, but the engine returned error for unknown guest agent ovirt-guest-agent. Moreover the ovirt-guest-agent conflicts rhev-guest-agent. This resulted in confusion among users. Fix: The engine now accounts for the renamed guest agent. Result: The engine no longer returns error for unknown guest agent.
Story Points: ---
Clone Of:
: 1464339 (view as bug list)
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3038081 None None None 2017-06-12 22:10 EDT

  None (edit)
Description Germano Veit Michel 2017-06-12 21:46:17 EDT
Description of problem:

Apparently in latest guest agent versions, we deprecated rhevm-guest-agent-common in favor of ovirt-guest-agent-common. But RHV vdc_option AgentAppName doesn't contain ovirt-guest-agent-common.

Freshly installed RHV 4.1 has these:

engine=# select option_name,option_value from vdc_options where option_name = 'AgentAppName';
 option_name  |                           option_value                           
 AgentAppName | rhev-agent,rhevm-guest-agent,rhevm-guest-agent-common,RHEV-Agent
(1 row)

Now install a fresh RHEL 7.3 and follow our documentation:

Note that at step 3 it asks to install:

3. Install the ovirt-guest-agent-common package and dependencies:

# yum install ovirt-guest-agent-common

That's not even on the list above. And even if I try to install "downstream" it won't without forcing a lower version, because ovirt-guest-agent-common obsoletes the rhevm-guest-agent, see:

# yum install rhevm-guest-agent-common
Package rhevm-guest-agent-common is obsoleted by ovirt-guest-agent-common, trying to install ovirt-guest-agent-common-1.0.13-5.el7ev.noarch instead
Resolving Dependencies
--> Running transaction check
---> Package ovirt-guest-agent-common.noarch 0:1.0.13-5.el7ev will be installed
--> Processing Dependency: qemu-guest-agent for package: ovirt-guest-agent-common-1.0.13-5.el7ev.noarch
--> Running transaction check
---> Package qemu-guest-agent.x86_64 10:2.5.0-3.el7 will be installed
--> Finished Dependency Resolution

 ovirt-guest-agent-common    noarch   1.0.13-5.el7ev   rhel-7-server-rh-common-rpms
Installing for dependencies:
 qemu-guest-agent            x86_64   10:2.5.0-3.el7   rhel-7-server-rpms

Then 'ovirt-guest-agent-common' not in [rhev-agent,rhevm-guest-agent,rhevm-guest-agent-common,RHEV-Agent] and we get this warning when trying to create a snapshot:

"Could not detect Guest Agent on the VM. Note that without a Guest Agent the data on the created snapshot may be inconsistent."

Version-Release number of selected component (if applicable):

How reproducible:
As above

Actual results:
Incorrect warning saying guest agent is missing

Expected results:
No warning
Comment 1 Tomas Jelinek 2017-06-13 06:33:48 EDT
in RHV 4.1 the GA is renamed to ovirt-guest-agent:

the rename from ovirt-guest-agent-* to rhev(m)-guest-agent-* is done as a part of the rhevm-setup-plugins (in setup/plugins/ovirt-engine-setup/rhevm-setup-plugins/distro-rhel/config.py)

Since RHV 4.1 needs to support also older guests we need to enrich the config to recognize/support both ovirt and rhv naming of the guest agent.
Comment 2 Germano Veit Michel 2017-06-15 23:52:14 EDT
Wouldn't it be a better idea to test communication with the agent and then forward this information to the engine than relying on forever chasing a set of package names?
Comment 3 Yaniv Kaul 2017-06-16 01:14:56 EDT
(In reply to Germano Veit Michel from comment #2)
> Wouldn't it be a better idea to test communication with the agent and then
> forward this information to the engine than relying on forever chasing a set
> of package names?

It would have been better to send the package version as part of the protocol (which would have been also more efficient than sending the applist and parsing it), but we are not planning to change the mechanism right now.
Comment 6 Petr Matyáš 2017-11-06 10:35:32 EST
Verified on ovirt-engine-4.2.0-0.0.master.20171106114404.git605a12f.el7.centos.noarch

Note You need to log in before you can comment on or make changes to this bug.