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.

+++ This bug was initially created as a clone of Bug #1117013 +++

cloud-init creates two files in /var/log:

/var/log/cloud-init.log
/var/log/cloud-init-output.log

policy should have defined both as cloud_log_t.

And, of course, cloud-init should have its own domain cloud_init_t.

Do we have the same bin path in RHEL6?

# ls -Z /usr/bin/cloud-init

The package is in epel.

# ls -Z /usr/bin/cloud-init
-rwxr-xr-x. root root system_u:object_r:bin_t:s0       /usr/bin/cloud-init

Does not look like we have cloud-init policy in rhel6.

Why is it a problem that these files are labeled var_log_t?

Yes, is this really issue in RHEL6?

If we don't see any issue I would keep it as we have it now.