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:

Running the Cockpit integration tests triggers these messages occasionally:

type=1400 audit(1454848791.816:4): avc: denied { append } for pid=1833 comm="rhsmcertd-worke" name="rhsm.log" dev="vda3" ino=25411401 scontext=system_u:system_r:rhsmcertd_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file
type=1400 audit(1454848792.184:5): avc: denied { append } for pid=1835 comm="rhsmcertd-worke" name="rhsm.log" dev="vda3" ino=25411401 scontext=system_u:system_r:rhsmcertd_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file

Version-Release number of selected component (if applicable):

subscription-manager-1.15.9-15.el7.x86_64
selinux-policy-targeted-3.13.1-60.el7.noarch

I initially reported that this happens on RHEL Atomic, but it actually happens on non-atomic RHEL.  Sorry for the confusion.

If this is not a selinux policy fix, please re-route back to subscription-manager with instructions on what we need to fix. Thanks

The rhsm.log file is mislabeled. Following command should fix it:

# restorecon -v /path/to/rhsm.log

Was SELinux enabled when the file was created ?

(In reply to Milos Malik from comment #4)

> Was SELinux enabled when the file was created ?

I think so.

# ls -Z /var/log/rhsm/rhsm.log 
-rw-r--r--. root root unconfined_u:object_r:rhsmcertd_log_t:s0 /var/log/rhsm/rhsm.log

I don't know when it is created.  I don't have a reliable way to reproduce this error, unforuntaly.  It happens very rarely.

After removing the file I wasn't able to provoke its recreation via "systemctl restart rhsmcertd", for example.