Bug 1278163
Summary: | incorrect ownership set on /dev/vport0p1 on RHEV guests, preventing guest agent from starting | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Allie DeVolder <adevolder> |
Component: | ovirt-guest-agent | Assignee: | Vinzenz Feenstra [evilissimo] <vfeenstr> |
Status: | CLOSED ERRATA | QA Contact: | Jiri Belka <jbelka> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.5.4 | CC: | adevolder, hannsj_uhl, lsurette, mgoldboi, mkenneth, omachace, rbalakri, redhat-bugzilla, robert.scheck, tjelinek, yeylon, ykaul |
Target Milestone: | ovirt-3.6.2 | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | rhevm-guest-agent-1.0.11-3.el7ev | Doc Type: | Bug Fix |
Doc Text: |
Cause: Previously the rules for udev haven't been reloaded on installation before attempting to trigger the newly installed udev rules.
Consequence: The communications device for the rhevm-guest-agent hasn't had the correct ownership and the rhevm-guest-agent wasn't able to start interacting with the device, causing the guest agent to fail on startup.
Fix: The installation rpms are now reloading the udev rules before attempting to trigger them.
Result: The ownership is now correctly set right after the first installation of the rhevm-guest-agent.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-10 16:57:05 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: | 1201513 |
Description
Allie DeVolder
2015-11-04 19:45:27 UTC
*** Bug 1278162 has been marked as a duplicate of this bug. *** Hi Allan, Please ask the customer for the the system journal. Additionally please check whether or not the following file is present: /etc/udev/rules.d/55-ovirt-guest-agent.rules If the file is present, please check whether or not the following command would solve the issue: # /sbin/udevadm trigger --subsystem-match="virtio-ports" --attr-match="name=com.redhat.rhevm.vdsm" # systemctl start ovirt-guest-agent.service The udev rule is supposed to set owner of the /dev/vport0p1 device to ovirtagent:ovirtagent, it seems like that it didn't get triggered, but why we have to figure out. Thanks Ok we have been able to reproduce that locally and the workaround for now is this: # udevadm trigger # systemctl start ovirt-guest-agent The problem is in the RPM it doesn't perform the trigger after the installation. An other solution is to restart the VM and it should work. ok, [root@10-34-60-161 ~]# ls -l /dev/vport2p* crw-rw----. 1 ovirtagent ovirtagent 248, 1 Dec 21 10:51 /dev/vport2p1 crw-------. 1 root root 248, 2 Dec 21 10:51 /dev/vport2p2 crw-------. 1 root root 248, 3 Dec 21 10:51 /dev/vport2p3 [root@10-34-60-161 ~]# rpm -q rhevm-guest-agent-common rhevm-guest-agent-common-1.0.11-3.el7ev.noarch 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://rhn.redhat.com/errata/RHEA-2016-0432.html |