RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

when selinux is disabled (not permissive) vdsm installation fails.


How reproducible:
100%

Steps to Reproduce:
1. disable selinux in /etc/selinux/config
2.install vdsm via ovirt.
3.
  
Actual results:
Sun, 08 Jan 2012 19:31:20 DEBUG    handleSSHKey start
Sun, 08 Jan 2012 19:31:20 DEBUG    handleSSHKey: failed to chmod authorized_keys
Traceback (most recent call last):
  File "/tmp/deployUtil.py", line 602, in handleSSHKey
    selinux.restorecon(P_ROOT_AUTH_KEYS)
  File "/usr/lib64/python2.7/site-packages/selinux/__init__.py", line 84, in restorecon
    status, oldcontext = lgetfilecon(path)

Expected results:

if selinux is not running, I would not try to change any selinux attributes.
Additional info:

Setting severity to high as this is an unexpected behavior introduced in 3.0.0 (0day) while fixing bug 746766.

http://gerrit.ovirt.org/1022

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
VDSM previously always attempted to update SELinux attributes, even when SELinux was disabled. This caused the installation to fail. 

The installation process has been modified to ensure that SELinux attributes are only modified if SELinux is enabled. This ensures that installation is still able to complete successfully when SELinux is disabled.

verified on vdsm-4.9.6-4.5.x86_64

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.

http://rhn.redhat.com/errata/RHSA-2012-1508.html