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 1998037 - podman 3.2.3: unknown capability "CAP_BPF"
Summary: podman 3.2.3: unknown capability "CAP_BPF"
Keywords:
Status: CLOSED DUPLICATE of bug 1921576
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libcap
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Zoltan Fridrich
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-26 10:24 UTC by Sebastian Wagner
Modified: 2021-09-09 17:58 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-27 09:29:16 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1946982 1 medium CLOSED unknown capability CAP_PERFMON 2024-12-20 19:55:52 UTC
Red Hat Issue Tracker RHELPLAN-95288 0 None None None 2021-08-26 10:32:57 UTC
Red Hat Issue Tracker SECENGSP-4059 0 None None None 2021-08-26 17:05:11 UTC

Description Sebastian Wagner 2021-08-26 10:24:25 UTC 
This is super similar to https://bugzilla.redhat.com/show_bug.cgi?id=1946982 but this time, We have a different error message: 

bash[26804]: Error: OCI runtime error: container_linux.go:370: starting container process caused: unknown capability "CAP_BPF"
systemd[1]: ceph-783410ce-0504-11ec-8c25-001a4aab830c.service: Control process exited, code=exited status=126
systemd[1]: ceph-783410ce-0504-11ec-8c25-001a4aab830c.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Ceph mon.a for 783410ce-0504-11ec-8c25-001a4aab830c.


This is the upstream run that failed: 

https://pulpito.ceph.com/pdonnell-2021-08-24_17:29:03-fs:workload-wip-pdonnell-testing-20210824.150835-distro-basic-smithi/6356265

Seems we tried running podman-3.2.3-0.10.module+el8.4.0+11989+6676f7ad.x86_64 on RHEL 8.4 and that combination seems to be broken. 

This is the podman run command that failed: 

/bin/podman run --rm --ipc=host --stop-signal=SIGTERM --net=host --entrypoint /usr/bin/ceph-mon --init -e CONTAINER_IMAGE=q
uay.ceph.io/ceph-ci/ceph:12c6370403d1ff9d4580beff2cfe964261fc5671 -e NODE_NAME=smithi023 -e CEPH_USE_RANDOM_NONCE=1 -v /var/log/ceph/783410ce-0504-11ec-8c25-001a4aab830c:/var/log/ceph:z -v /var/lib/ceph/783410ce
-0504-11ec-8c25-001a4aab830c/mon.a:/var/lib/ceph/mon/ceph-a:z -v /tmp/ceph-tmpymo1jjtl:/tmp/keyring:z -v /tmp/ceph-tmpq13q9m8_:/tmp/monmap:z quay.ceph.io/ceph-ci/ceph:12c6370403d1ff9d4580beff2cfe964261fc5671 --m
kfs -i a --fsid 783410ce-0504-11ec-8c25-001a4aab830c -c /dev/null --monmap /tmp/monmap --keyring /tmp/keyring --setuser ceph --setgroup ceph --default-log-to-file=false --default-log-to-journald=true --default-l
og-to-stderr=false --default-mon-cluster-log-to-file=false --default-mon-cluster-log-to-journald=true --default-mon-cluster-log-to-stderr=false

Unfortunately, I don't know which libcap version is installed on that host.
Comment 2 Zoltan Fridrich 2021-08-27 09:29:16 UTC 
This is a duplicate of rhbz#1921576
in both cases the CAP_BPF is undefined.

*** This bug has been marked as a duplicate of bug 1921576 ***
Comment 3 Sebastian Wagner 2021-09-09 17:58:50 UTC 
For the record, the fix is: https://github.com/ceph/ceph/blob/61be1d923d122a38f4cb4e4080f8521ae8b5a19b/qa/distros/podman/rhel_8.4_container_tools_rhel8.yaml#L12
Note You need to log in before you can comment on or make changes to this bug.