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 systemd-hostnamed service is restarted or hostnamectl command is issued, the child of systemd (which will later be systemd-hostnamed) remounts all file systems read-only (MS_RDONLY) as per service unit policy (ProtectXXX stanzas). SELinux blocks ostnamed from remounting container_ro_file_t filesystems.


Version-Release number of selected component (if applicable):
RHEL 8.2, RHEL 8.4 (reproduced on both)


How reproducible:
Restart systemd-hostnamed service or issue hostnamectl command on host with podman containers and container_ro_file_t mounts (RHOSP Compute nodes specifically).

Actual results:
SELinux is preventing ostnamed from remounting container_ro_file_t filesystems

Expected results:
SELinux is allowing ostnamed from remounting container_ro_file_t filesystems

Additional info:
Will provide in private follow-up

Commit to backport:
commit e08c435d047d12cf06a4749b963035c34cbb2225
Author: Zdenek Pytela <zpytela>
Date:   Wed Sep 7 09:41:19 2022 +0200

    Allow init remount all file_type filesystems

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 (selinux-policy bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2023:2965