Description: # /etc/init.d/virt-who start Starting virt-who: /usr/bin/python: can't open file '/usr/share/virt-who/virtwho.py': [Errno 2] No such file or directory [FAILED] Test Steps: 1. installed RHEV-H 6.6 for 3.5 successful. 2. Check virt-who status, virt-who service is stop. 3. run cmd manually to start virt-who service, failed. # /etc/init.d/virt-who status virt-who is stopped # /etc/init.d/virt-who start Starting virt-who: /usr/bin/python: can't open file '/usr/share/virt-who/virtwho.py': [Errno 2] No such file or directory [FAILED] # rpm -qa|grep virt-who virt-who-0.10-8.el6.noarch Test version virt-who-0.10-8.el6.noarch rhev-hypervisor6-6.6-20141008.0.iso ovirt-node-3.1.0-0.22.20141010git96b7ca3.el6 Actual result: virt-who service is stop after rhevh installation. expected result: virt-who service should run as default after rhevh installation. Note: this bug is testblocker as it block entitlement QE testing.
this bug occur on rhevh 6.6 for 3.4.z too, to get fresh info for such issue on rhevh 6.6 for 3.4.z, I open new rhevh 6.6 for 3.4.z bug 1158497
Patch 34413 merged yet, but still encounter this bug on rhevh build, so assgined it. rhev-hypervisor6-6.6-20141107.0.iso ovirt-node-3.1.0-0.25.20141107gitf6dc7b9.el6 ovirt-node-recipe-3.1.0-0.25.20141107gitf6dc7b9.el6.noarch.rpm # /etc/init.d/virt-who start Starting virt-who: /usr/bin/python: can't open file '/usr/share/virt-who/virtwho.py': [Errno 2] No such file or directory [FAILED]
Added another patch which is also needed.
# /etc/init.d/virt-who status virt-who (pid 16241) is running... # rpm -qa|grep ovirt-node ovirt-node-3.1.0-0.27.20141119git24e087e.el6.noarch # rpm -qa|grep virt-who virt-who-0.10-8.el6.noarch # cat /etc/system-release Red Hat Enterprise Virtualization Hypervisor release 6.6 (20141119.0.el6ev) virt-who service is running as default after rhevh installation. So this bug is fixed. After this bug change to ON_QA, I will make it as 'VERIFIED' status.
according to comment 5, change it to VERIFIED.
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-2015-0160.html