Yaniv, from 3.5.4 on RHEV-H will keep the libvirtd upstart file. IIRC there are also some adjustments on the vdsm side needed - specififc to RHEV-H - to use that file on RHEV-H. Could you check if the upstart file will now be used on RHEV-H if available?
Yep , https://gerrit.ovirt.org/#/c/42973/ removes the node restriction - without the explicit condition we will have libvirtd respawn also in el6 RHEV-H . How do we verify it? should we have vdsm separate bug for that change?
Oved, adding you to the needinfo about creating separate bugzilla question - as it is vdsm infra issue that should be handled in 3.5 scope.
From the testing perspective I'd say yes to two bugs: 1. This node bug for ensuring that the upstart file is in place 2. vdsm bug to check that the logic is really restarting libvirtd in case it goes down.
*** Bug 1235349 has been marked as a duplicate of this bug. ***
*** Bug 1239285 has been marked as a duplicate of this bug. ***
Test steps to test this bug: (A) 1. Install RHEV-H manually 2. Register to RHEV-M 3.5 (from TUI side) 3. Setup storage, networking etc 4. Launch a VM, make sure it is launched correctly 5. Launch a second VM, make sure it is launched correctly. Second test: As in (A) but in 2.: Add from Engine side Third test: As in (A) but in 1.: Use auto-install + management_server (registration) Fourth test: As in (A) but in 1.: Use auto-install WITHOUT management_server and add from Engine side.
In addition to comment 9: 6. Put RHEV-H into maintenance mode and reboot 7. Make sure all VMs come up again afterwards
According to patches, the testing as following: Test version: # rpm -qa ovirt-node ovirt-node-3.2.3-11.el6.noarch # cat /etc/redhat-release Red Hat Enterprise Virtualization Hypervisor release 6.7 (20150717.0.el6ev) # rpm -qa libvirt libvirt-0.10.2-54.el6.x86_64 # ll /usr/share/doc/libvirt-0.10.2/libvirtd.upstart -rw-r--r--. 1 root root 1181 2015-07-17 15:07 /usr/share/doc/libvirt-0.10.2/libvirtd.upstart # ll /etc/init/libvirtd.conf -rw-r--r--. 1 root root 1181 2015-07-23 07:28 /etc/init/libvirtd.conf libvirtd.upstart already kept under /usr/share/doc/libvirt-0.10.2 and already copy to /etc/init/libvirtd.conf
Before registration it should actually not be in /etc/init/libvirtd.conf Ying, did you check the existence of /etc/init/libvirtd.conf before or after registration? After a clean install libvirtd.conf should only be in /usr/share/doc/libvirt-0.10.2/libvirtd.upstart
Let me correct myself: /etc/init/libvirtd.conf will be there, because vdsm-tool is installing it at boot time.
Fabian, now the vdsm bug 1236489 is closed as won't fix. So we will verify this bug according to comment 14 on node side, OK?
Ying, ok.
for patches on this bug, here only care rhevh 6.7, not impact rhevh 7.1. according to to comment 14, comment 18 and comment 19, Verified this bug on rhevh 6.7.
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/RHBA-2015-1733.html