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:
oci-seccomp-bpf-hook pulls in kernel-devel package via its bcc dependency - this largely inflates the dependency footprint of the whole container-tools:
L 4.1M oci-seccomp-bpf-hook 1.2.0-1.fc32.x86_64
o 78.2M ├─> bcc 0.15.0-2.fc31.x86_64
o 1.8M │ ├─>+bcc-tools 0.15.0-2.fc31.x86_64
o 7.2M │ │ ├─> bash 5.0.17-1.fc31.x86_64
935K │ │ ├─> elfutils-libelf 0.179-2.fc31.x86_64
o 16.5M │ │ ├─> glibc 2.30-13.fc31.x86_64
50.7M │ │ ├─> kernel-devel 5.7.15-100.fc31.x86_64
o 32K │ │ ├─> python3 3.7.9-1.fc31.x86_64
o 320K │ │ ├─>+python3-bcc 0.15.0-2.fc31.noarch
8.3M │ │ ├─> python3-netaddr 0.7.19-17.fc31.noarch
201K │ │ └─> zlib 1.2.11-20.fc31.x86_64
The plan is to make this package optional in container-tools if module subsystem allows to.
Checked the filelist from errata and check rpms after install the packages. Seems the oci-seccomp-bpf-hook is not installed as expect. So set this to verified.
Close this as VERIFIED according to the following testing.
# yum module info container-tools:rhel8|grep oci-seccomp-bpf-hook
: oci-seccomp-bpf-hook-0:1.1.2-3.module+el8.3.0+8049+d0453aae.src
: oci-seccomp-bpf-hook-0:1.1.2-3.module+el8.3.0+8049+d0453aae.x86_64
: oci-seccomp-bpf-hook-debuginfo-0:1.1.2-3.module+el8.3.0+8049+d0453aae.x86_64
: oci-seccomp-bpf-hook-debugsource-0:1.1.2-3.module+el8.3.0+8049+d0453aae.x86_64
NOTE: the oci-seccomp-bpf-hook belongs to container-tools:rhel8
# yum module install container-tools:rhel8
NOTE: the oci-seccomp-bpf-hook is not a dependency of the container-tools:rhel8
# yum install oci-seccomp-bpf-hook
NOTE: can install oci-seccomp-bpf-hook rpm separately.
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 (Moderate: container-tools:rhel8 security, 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/RHSA-2020:4694
Description of problem: oci-seccomp-bpf-hook pulls in kernel-devel package via its bcc dependency - this largely inflates the dependency footprint of the whole container-tools: L 4.1M oci-seccomp-bpf-hook 1.2.0-1.fc32.x86_64 o 78.2M ├─> bcc 0.15.0-2.fc31.x86_64 o 1.8M │ ├─>+bcc-tools 0.15.0-2.fc31.x86_64 o 7.2M │ │ ├─> bash 5.0.17-1.fc31.x86_64 935K │ │ ├─> elfutils-libelf 0.179-2.fc31.x86_64 o 16.5M │ │ ├─> glibc 2.30-13.fc31.x86_64 50.7M │ │ ├─> kernel-devel 5.7.15-100.fc31.x86_64 o 32K │ │ ├─> python3 3.7.9-1.fc31.x86_64 o 320K │ │ ├─>+python3-bcc 0.15.0-2.fc31.noarch 8.3M │ │ ├─> python3-netaddr 0.7.19-17.fc31.noarch 201K │ │ └─> zlib 1.2.11-20.fc31.x86_64 The plan is to make this package optional in container-tools if module subsystem allows to.