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.
I'm seeing:
type=AVC msg=audit(1404835626.233:83): avc: denied { read } for pid=827 comm="rhsmcertd-worke" name="ostree" dev="sda3" ino=8389295 scontext=system_u:system_r:rhsmcertd_t:s0 tcontext=system_u:object_r:default_t:s0 tclass=lnk_file
See also https://bugzilla.redhat.com/show_bug.cgi?id=1115212
The right fix may be an updated SELinux policy.
Normally most userspace processes shouldn't need access to /ostree (or /sysroot), but subscription-manager right now writes to /ostree/repo/config.
Can we just allow this access in RHEL7?
rhsmcertd-worker will need to:
- read /ostree/repo/config
- write /ostree/repo/config
/usr/share/rhsm/subscription_manager/plugin/ostree/gi_wrapper.py
will need to be able to read/write
/ostree/deploy/rhel-atomic-host/deploy/*.origin
(and likely..
/ostree/deploy/*/deploy/*.origin
If those files get specific contexts, subscription-manager will
need to be able to read/write as well.
How are /ostree/repo and /ostree/deploy/*/deploy dirs placed? Basically I will add mnt_t label for /ostree but we will need to add filenametrans for these subdirs to get correct labeling.
mnt_t would be strange for /ostree. I think usr_t would be a better match.
Right now these files are generated by Anaconda, which calls into ostree itself to initialize the rootfs. I think we can take care of just looking up the label for /usr and using that as the context for these files.
I'm seeing: type=AVC msg=audit(1404835626.233:83): avc: denied { read } for pid=827 comm="rhsmcertd-worke" name="ostree" dev="sda3" ino=8389295 scontext=system_u:system_r:rhsmcertd_t:s0 tcontext=system_u:object_r:default_t:s0 tclass=lnk_file See also https://bugzilla.redhat.com/show_bug.cgi?id=1115212 The right fix may be an updated SELinux policy.