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:
hostnamectl generates AVC denial on s390x

Version-Release number of selected component (if applicable):
systemd-219-8.el7.s390x


Steps to Reproduce:
1. Run /CoreOS/systemd/Sanity/hostnamectl  on s390x

Actual results:
time->Mon Jul 27 08:53:18 2015
type=SYSCALL msg=audit(1438001598.519:55): arch=80000016 syscall=5 success=no exit=-13 a0=2aa007492f4 a1=80000 a2=1b6 a3=80000 items=0 ppid=1 pid=12428 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-hostnam" exe="/usr/lib/systemd/systemd-hostnamed" subj=system_u:system_r:systemd_hostnamed_t:s0 key=(null)
type=AVC msg=audit(1438001598.519:55): avc:  denied  { read } for  pid=12428 comm="systemd-hostnam" name="sysinfo" dev="proc" ino=4026531902 scontext=system_u:system_r:systemd_hostnamed_t:s0 tcontext=system_u:object_r:sysctl_t:s0 tclass=file

Expected results:
No denials

Additional info:
Beaker run: https://beaker.engineering.redhat.com/recipes/2108210

Is this still reproducible with newest versions of SELinux policy and systemd?

selinux-policy-3.13.1-60.el7.noarch
systemd-219-19.el7_2.3.s390x


time->Fri Jan  8 13:23:38 2016
type=SYSCALL msg=audit(1452277418.115:101): arch=80000016 syscall=5 success=no exit=-13 a0=2aa0019e2cc a1=80000 a2=1b6 a3=80000 items=0 ppid=1 pid=11276 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-hostnam" exe="/usr/lib/systemd/systemd-hostnamed" subj=system_u:system_r:systemd_hostnamed_t:s0 key=(null)
type=AVC msg=audit(1452277418.115:101): avc:  denied  { read } for  pid=11276 comm="systemd-hostnam" name="sysinfo" dev="proc" ino=4026531902 scontext=system_u:system_r:systemd_hostnamed_t:s0 tcontext=system_u:object_r:sysctl_t:s0 tclass=file

Needs to be retested with 219-30.

This seems to be fixed now.

https://beaker.engineering.redhat.com/jobs/1645669

Brano, please double check and reopen if necessary.