Bug 1401183 - ovirt-guest-agent cannot be detected and therefore "data on the created snapshot may be inconsistent"
Summary: ovirt-guest-agent cannot be detected and therefore "data on the created snaps...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
high
medium vote
Target Milestone: ---
: ---
Assignee: Daniel Erez
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On: 1300566
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-03 11:17 UTC by Raz Tamir
Modified: 2017-10-02 13:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-04 09:20:37 UTC
oVirt Team: Virt


Attachments (Terms of Use)
engine and vdsm logs (22.63 KB, application/x-gzip)
2016-12-04 09:51 UTC, Raz Tamir
no flags Details

Description Raz Tamir 2016-12-03 11:17:30 UTC
Description of problem:
On a VM with OS and with ovirt-guest-agent and qemu-guest-agent installed and running:
[root@localhost ~]# service qemu-guest-agent status
Redirecting to /bin/systemctl status  qemu-guest-agent.service
● 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 Sat 2016-12-03 10:24:43 IST; 2h 24min ago
 Main PID: 493 (qemu-ga)
   CGroup: /system.slice/qemu-guest-agent.service
           └─493 /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-f...

Dec 03 10:24:43 localhost.localdomain systemd[1]: Started QEMU Guest Agent.
Dec 03 10:24:43 localhost.localdomain systemd[1]: Starting QEMU Guest Agent...
[root@localhost ~]# service rhevm-guest-agent status
Redirecting to /bin/systemctl status  rhevm-guest-agent.service
● rhevm-guest-agent.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
[root@localhost ~]# service ovirt-guest-agent status
Redirecting to /bin/systemctl status  ovirt-guest-agent.service
● 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 Sat 2016-12-03 10:24:44 IST; 2h 24min ago
  Process: 545 ExecStartPre=/bin/chown ovirtagent:ovirtagent /run/ovirt-guest-agent.pid (code=exited, status=0/SUCCESS)
  Process: 540 ExecStartPre=/bin/touch /run/ovirt-guest-agent.pid (code=exited, status=0/SUCCESS)
  Process: 495 ExecStartPre=/sbin/modprobe virtio_console (code=exited, status=0/SUCCESS)
 Main PID: 549 (python)
   CGroup: /system.slice/ovirt-guest-agent.service
           └─549 /usr/bin/python /usr/share/ovirt-guest-agent/ovirt-guest-agent.py

When trying to create a live snapshot with memory, the message 
"Could not detect Guest Agent on the VM. Note that without a Guest Agent the data on the created snapshot may be inconsistent." appears.



Version-Release number of selected component (if applicable):
ovirt-engine-4.1.0-0.0.master.20161126211319.gitae69c34.el7.centos.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create live snapshot
2.
3.

Actual results:
In the dialog window, a message appears

Expected results:


Additional info:
- In 4.0.z the message isn't there
- no logs needed

Comment 1 Allon Mureinik 2016-12-04 09:03:21 UTC
Raz, we need the logs please (engine and VDSM).

Comment 2 Raz Tamir 2016-12-04 09:51:22 UTC
Created attachment 1227903 [details]
engine and vdsm logs

Logs attached

Comment 3 Red Hat Bugzilla Rules Engine 2016-12-27 07:19:26 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 4 Yaniv Lavi 2017-01-02 12:46:06 UTC
Moving to virt.

Comment 5 Tomas Jelinek 2017-01-03 09:15:35 UTC
It seems that you have the RHV and oVirt env mixed up. The guest seems to have the "rhevm-guest-agent" while the engine looks like ovirt. Engine tries to look for the guest agent by name defined in vdc_options as AgentAppName which for ovirt is set as ovirt-guest-agent-common,ovirt-guest-agent.

You can fix it by one of this things:
- Add this guest to RHV
- Install oVirt GA instead of RHV one to this machine guest

Comment 6 Tomas Jelinek 2017-01-04 09:20:10 UTC
anyway, closing as not a bug for now. Please feel free to reopen if it happens also with correct combination of GA and engine.

Comment 7 Raz Tamir 2017-01-10 16:27:10 UTC
Thanks for clarifying this Tomas.
After tested this on RHV instead of oVirt with the same VM, this seems to behave as expected

Comment 8 Sandro Bonazzola 2017-10-02 13:30:11 UTC
Just a note here, we fixed this in RHV-M 4.1.4 with bug #1464339


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