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.

See:
https://bugzilla.redhat.com/show_bug.cgi?id=1309075
and
https://github.com/projectatomic/rpm-ostree/pull/292

This is now an active time bomb in RHELAH 7.

Can we:

0) Ensure this is fixed in 7.3
1) Backport the fix into the current stable 7.2 SELinux policy package
2) Tag that package into the RHELAH 7 stream
3) Remember to un-tag the override when rebasing to 7.3

Related to this...as I discussed in the PR, is there a reason we're not using rpm_t as PackageKit already does?

(In reply to Colin Walters from comment #1)
> Related to this...as I discussed in the PR, is there a reason we're not
> using rpm_t as PackageKit already does?

Can someone reply to this aspect please?

And related to this, can the policy be changed to set this *both* on /usr/bin/rpm-ostree and /usr/libexec/rpm-ostreed (which may not exist after the above linked PR lands)

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, 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://rhn.redhat.com/errata/RHBA-2016-2283.html