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:
Hello there,

There's apparently an issue with container-selinux 3:2.191.0-1.el9 on CS9: it can't get properly installed, failing with this error:

Failed to resolve allow statement at /var/lib/selinux/targeted/tmp/modules/200/container/cil:1219

After a check of that CIL file, it happens to be this line:

(allow container_domain init_t (bridge_socket (ioctl read write getattr lock append accept getopt)))

Apparently, that bridge_socket was removed from selinux-policy in this patch

Downgrading selinux-policy (as well as selinux-policy-targeted) to 34.1.47-1.el9 allows to properly install container-selinux, without any issue.

Care to have a look?

Thank you!

Cheers,

C.

PS: this opened on request from the original github issue:
https://github.com/containers/container-selinux/issues/198

Unused security classes were removed as a side effect of policy sources rebase in selinux-policy-38.1.1-1.el9.
Please use selinux-policy-38.1.2-1.el9.

I thinks this bz can be closed as a dup of bz#2145266.

Zdenek, assuming we need to amend the "at least" dependency on selinux-policy-38.1.2-1.el9 in container-selinux so I will keep this open to track this.

(In reply to Jindrich Novy from comment #2)
> Zdenek, assuming we need to amend the "at least" dependency on
> selinux-policy-38.1.2-1.el9 in container-selinux so I will keep this open to
> track this.

OK. Also note selinux-policy versions up to 34.1.47-1 contained the classes as well.

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 (container-selinux bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2023:2206