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.
Bug 2026372 - container-selinux version
Summary: container-selinux version
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: container-tools-2.0-module
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-24 13:53 UTC by Julie Pichon
Modified: 2021-12-03 21:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-03 21:28:13 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2020210 1 urgent CLOSED [FFWD 13 ->16.2] Controller upgrade fails due to inactive rabbitmq (PermissionError: [Errno 13] Permission denied: '/var... 2022-08-08 12:02:54 UTC
Red Hat Issue Tracker RHELPLAN-103845 0 None None None 2021-11-24 13:54:54 UTC

Description Julie Pichon 2021-11-24 13:53:21 UTC 
Description of problem:

A recent update to container-selinux in container-tools:3.0 broke OSP 16.2 on RHEL 8.4 (see bug 2020210). This is because the new package includes commit 7e5f3c [1] which added a new file context for a generic path name (/var/log/containers) that is also in use by OpenStack - with different label expectations.

OSP 16.1 runs on container-tools:2.0 which thankfully doesn't have this patch yet. Our fix for 16.2 doesn't apply cleanly because it assumes the newer container-selinux package is also present.

Ideally, the problematic patch [1] would not be backported to container-tools:2.0 to avoid breaking current OSP 16.1 customers.

However, I am not sure about the roadmap. Are there any plans to update container-selinux in the container-tools:2.0 module stream? If so, could this update be coordinated with OSP/openstack-selinux, as a heads-up would be useful to make sure we are also ready? Thank you.

[1] https://github.com/containers/container-selinux/commit/7e5f3cae10e2d805821fb84dff7418b9e3b0cc1f

Version-Release number of selected component (if applicable):
container-selinux-2.124.0-1.module+el8.2.0+11121+714aca16.src.rpm works fine with OSP on 8.2.
Comment 2 Daniel Walsh 2021-12-01 20:55:25 UTC 
I know of know plans to back port, but if so, yes we could coordinate and remove our label of /var/log/containers.
Comment 3 Jindrich Novy 2021-12-02 11:50:56 UTC 
Currently we have no plans to update container-selinux in 2.0-8.4.0. If I read the bugreport right - the label of /var/log/containers needs to be removed from 3.0-8.4.0?
Comment 4 Julie Pichon 2021-12-02 13:34:14 UTC 
Thank you for the replies! The new label is fine from container-tools:3.0 onward, there is no need to remove/revert it because we've already patched OSP 16.2+ to expect it now. This bug is only about the container-selinux version in the container-tools:2.0 stream which OSP 16.1 uses.
Comment 5 Daniel Walsh 2021-12-02 14:10:14 UTC 
I think this is only if we were to ship an update.
Comment 6 Tom Sweeney 2021-12-02 15:49:40 UTC 
Yes, I think the issue is set for now, but we have to be careful about updating selinux in container-tools:2.0 going forward.  We have no plans to do so, my fear is a CVE will come in 6 months from now and we will have forgotten this dependency.

I'm going to make a note to myself, Jindrich and Dan if you could do the same, hopefully, one of us will remember if the need arises.

Given that, Jesse, can we close this issue?
Comment 7 Julie Pichon 2021-12-02 17:31:53 UTC 
From my perspective, I'm happy for the issue to be closed. I wanted to raise awareness, as long as we can get some heads-up for container-tools:2.0 updates this should be fine. Thank you.
Note You need to log in before you can comment on or make changes to this bug.