This bug is for rhevh 6.6 for 3.4.z. for 3.5 bug is 1152414[POST]. Description: # /etc/init.d/virt-who start Starting virt-who: /usr/bin/python: can't open file '/usr/share/virt-who/virt-who.pyc': [Errno 2] No such file or directory [FAILED] Test Steps: 1. installed RHEV-H 6.6 for 3.4.z 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/virt-who.pyc': [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 Red Hat Enterprise Virtualization Hypervisor release 6.6 (20141024.0.el6ev) ovirt-node-3.0.1-19.el6.18.noarch 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.
The cause of this is exactly the same as that of bz#1152414 -- there were some changes in virt-who which are normally invisible, but the path change affects RHEV-H because we strip uncompiled python and sometimes (virt-who, sos) assume some pyc files will be there which are not.
move out flag rhevm 3.5.0?, for rhev 3.5 bug, we will use 1152414[MODIFIED] to trace.
Done
Verified this bug on build: ovirt-node-3.0.1-19.el6.23.noarch virt-who-0.10-8.el6.noarch Red Hat Enterprise Virtualization Hypervisor release 6.6 (20141112.0.el6ev) virt-who is running as default and no error pop up after rhevh installation, and the virt-who service can stop/restart/start correctly, no error. So this bug is fixed.
Hi Ryan, If this bug requires doc text for errata release, please provide draft text in the following format: Cause: Consequence: Fix: Result: The documentation team will review, edit, and approve the text. If this bug does not require doc text, please set the 'requires_doc_text' flag to -. Many thanks, Julie
3.4.4 was released. moving to async release 3.4.4-1, only for RHEV-H
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-0128.html