Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
On a newly installed system I have:
# ls -Zd /etc/multipath
drwxr-xr-x. root root system_u:object_r:root_t:s0 /etc/multipath
# rpm -qa | grep multipath
# for P in `rpm -qa`; do rpm -q --scripts $P | grep -q multipath && echo $P; done
#
# ls -lZR /etc/multipath
/etc/multipath:
-rw-------. root root system_u:object_r:root_t:s0 bindings
but the correct context is lvm_metadata_t (see bug 880407).
in anaconda.log I can see:
11:21:28,431 INFO : moving (1) to step preinstallconfig
11:21:28,432 DEBUG : preinstallconfig is a direct step
11:21:28,456 DEBUG : isys.py:mount()- going to mount /selinux on /mnt/sysimage/selinux as selinuxfs with options defaults
11:21:28,459 DEBUG : isys.py:mount()- going to mount /proc/bus/usb on /mnt/sysimage/proc/bus/usb as usbfs with options defaults
11:21:28,467 INFO : copy_to_sysimage: source '/etc/multipath/wwids' does not exist.
11:21:28,467 DEBUG : copy_to_sysimage: '/etc/multipath/bindings' -> '/mnt/sysimage/etc/multipath/bindings'.
11:21:28,474 INFO : copy_to_sysimage: source '/etc/multipath/wwids' does not exist.
11:21:28,474 DEBUG : copy_to_sysimage: '/etc/multipath/bindings' -> '/mnt/sysimage/etc/multipath/bindings'.
11:21:28,477 INFO : leaving (1) step preinstallconfig
seems that the context should be restored later on.
How reproducible:
always on the necessary system configuration
Steps to Reproduce:
1. just install the system
2. check /etc/multipath/binding
3.
Actual results:
/etc/multipath directory has wrong selinux context
Expected results:
/etc/multipath (and its content) has correct selinux context
Additional info:
Comment 3RHEL Program Management
2013-05-06 21:15:57 UTC
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
Comment 10Samantha N. Bueno
2013-07-02 01:13:12 UTC
Created attachment 767576[details]
possible fix
I'm attaching an updates.img with a proposed fix. Would someone mind testing this out to verify the correct SELinux context is being set now?
Comment 11Samantha N. Bueno
2013-07-02 01:41:13 UTC
Created attachment 767581[details]
updates.img w/possible fix
Bah; please ignore that first attachment and use this updates.img to test. (Sorry about that.)
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/RHBA-2013-1588.html