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:
rhel 7 ubi does not pass rpm Verification for shadow-utils rpm
Version-Release number of selected component (if applicable):
How reproducible:
Everytime
Steps to Reproduce:
1.# podman run --rm -it registry.access.redhat.com/ubi7/ubi:latest /bin/bash
2.# rpm -V shadow-utils
3.
Actual results:
........P /usr/bin/newgidmap
........P /usr/bin/newuidmap
Expected results:
<no output>
Additional info:
Using getcap, nothing is set on the files. Reinstalling shows what should be set.
# getcap /usr/bin/*idmap
<no output>
# yum reinstall shadow-utils -y
# getcap /usr/bin/*idmap
/usr/bin/newgidmap = cap_setgid+ep
/usr/bin/newuidmap = cap_setuid+ep
This does appear to be specific to the image, or at least it doesn't seem to be something that podman/overlayfs is doing to the image/container
Looking at just the image layers:
# mkdir /tmp/test
# skopeo copy docker://registry.access.redhat.com/ubi7:latest dir:/tmp/test
Getting image source signatures
Copying blob 1323a241cc06 done
Copying blob 2bd25ca12457 done
Copying config fdef99b341 done
Writing manifest to image destination
Storing signatures
# tar xvf /tmp/test/1323a241cc068f2816dd88f00168be73339471d6dc6eb2e6c761b63b734501b6 ./usr/bin/newuidmap
./usr/bin/newuidmap
# ls -l /root/usr/bin/newuidmap
-rwxr-xr-x. 1 root root 38976 May 3 2019 /root/usr/bin/newuidmap
# getcap -v /root/usr/bin/newuidmap
/root/usr/bin/newuidmap
I would guess their stripped during the image build process somehow.
FWIW it seems upstream Fedora also has the problem, probably because they use the same tooling to build their image.
In https://www.redhat.com/sysadmin/podman-inside-container
First pull fedora latest, and then update to the latest packages.
Note it reinstalls shadow-utils, since there is a known issue in the shadow-utils install on the Fedora image where the filecaps on newsubuid and newsubgid are not set.
The oc bug is fixed in 4.7.z and should be fixed soon in 4.6.z and 4.8. The opm bug is fixed in 4.6.z and 4.7.z, and it should be fixed soon in 4.8. I think it will be safe to reintroduce this change with 8.5.
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 (Red Hat Universal Base Image 8 Container Image 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-2021:4551