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:
After update of RHEL-8.1.0 compose from RHEL-8.1.0-20190604.7 to RHEL-8.1.0-20190619.2 I hit following selinux denial:
time->Sun Jul 7 11:06:22 2019
type=PROCTITLE msg=audit(1562511982.369:33): proctitle=2F7362696E2F6468636C69656E74002D64002D71002D7366002F7573722F6C6962657865632F6E6D2D646863702D68656C706572002D7066002F72756E2F4E6574776F726B4D616E616765722F6468636C69656E742D657468302E706964002D6C66002F7661722F6C69622F4E6574776F726B4D616E616765722F6468636C69
type=SYSCALL msg=audit(1562511982.369:33): arch=c000003e syscall=257 success=no exit=-13 a0=ffffff9c a1=7ffea51c0e9a a2=80241 a3=1a4 items=0 ppid=811 pid=884 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dhclient" exe="/usr/sbin/dhclient" subj=system_u:system_r:dhcpc_t:s0 key=(null)
type=AVC msg=audit(1562511982.369:33): avc: denied { write } for pid=884 comm="dhclient" name="NetworkManager" dev="tmpfs" ino=22589 scontext=system_u:system_r:dhcpc_t:s0 tcontext=system_u:object_r:NetworkManager_var_run_t:s0 tclass=dir permissive=0
I have this modification of NetworkManager configuration:
echo -e "[main]\ndhcp=dhclient" > /etc/NetworkManager/conf.d/lnst.conf
There were two changes between the two composes that may have caused this issue:
selinux-policy-3.14.3-7.el8 -> selinux-policy-3.14.3-9.el8
NetworkManager-1:1.14.0-14.el8 -> NetworkManager-1:1.20.0-0.1.el8
Version-Release number of selected component (if applicable):
NetworkManager-1:1.20.0-0.1.el8
selinux-policy-3.14.3-9.el8
How reproducible:
100%
Steps to Reproduce:
1. clone this beaker job https://beaker.engineering.redhat.com/jobs/3654957
or simply setup NetworkManager to use dhclient for DHCP instead of internal one that seems to work without any issues
2.
3.
Actual results:
selinux denial
Expected results:
no selinux denial
Additional info:
Comment 1Beniamino Galvani
2019-08-07 08:56:23 UTC
Description of problem: After update of RHEL-8.1.0 compose from RHEL-8.1.0-20190604.7 to RHEL-8.1.0-20190619.2 I hit following selinux denial: time->Sun Jul 7 11:06:22 2019 type=PROCTITLE msg=audit(1562511982.369:33): proctitle=2F7362696E2F6468636C69656E74002D64002D71002D7366002F7573722F6C6962657865632F6E6D2D646863702D68656C706572002D7066002F72756E2F4E6574776F726B4D616E616765722F6468636C69656E742D657468302E706964002D6C66002F7661722F6C69622F4E6574776F726B4D616E616765722F6468636C69 type=SYSCALL msg=audit(1562511982.369:33): arch=c000003e syscall=257 success=no exit=-13 a0=ffffff9c a1=7ffea51c0e9a a2=80241 a3=1a4 items=0 ppid=811 pid=884 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dhclient" exe="/usr/sbin/dhclient" subj=system_u:system_r:dhcpc_t:s0 key=(null) type=AVC msg=audit(1562511982.369:33): avc: denied { write } for pid=884 comm="dhclient" name="NetworkManager" dev="tmpfs" ino=22589 scontext=system_u:system_r:dhcpc_t:s0 tcontext=system_u:object_r:NetworkManager_var_run_t:s0 tclass=dir permissive=0 I have this modification of NetworkManager configuration: echo -e "[main]\ndhcp=dhclient" > /etc/NetworkManager/conf.d/lnst.conf There were two changes between the two composes that may have caused this issue: selinux-policy-3.14.3-7.el8 -> selinux-policy-3.14.3-9.el8 NetworkManager-1:1.14.0-14.el8 -> NetworkManager-1:1.20.0-0.1.el8 Version-Release number of selected component (if applicable): NetworkManager-1:1.20.0-0.1.el8 selinux-policy-3.14.3-9.el8 How reproducible: 100% Steps to Reproduce: 1. clone this beaker job https://beaker.engineering.redhat.com/jobs/3654957 or simply setup NetworkManager to use dhclient for DHCP instead of internal one that seems to work without any issues 2. 3. Actual results: selinux denial Expected results: no selinux denial Additional info: