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:
I can't use atomic-pkglayer to install docker-latest related RPM packages on Atomic Host, and got "GLib.Error: g-io-error-quark: openat: No such file or directory (1)"
Version-Release number of selected component (if applicable):
registry.access.redhat.com/rhel7/rhel-tools:latest (3b7bd2d69242)
[cloud-user@atomic-00 ~]$ rpm -q docker atomic
docker-1.9.1-26.el7.x86_64
atomic-1.9-4.gitff44c6a.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. docker pull registry.access.redhat.com/rhel7/rhel-tools
2. docker run -it registry.access.redhat.com/rhel7/rhel-tools:latest
3. download docker-latest related RPM packages in rhel-tools container
4. using atomic-pkglayer to install these RPM packages
Actual results:
[root@b00c0ce22e3f docker-latest]# ls
docker-latest-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm docker-latest-selinux-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm
docker-latest-fish-completion-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm docker-latest-utils-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm
docker-latest-forward-journald-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm docker-latest-v1.10-migrator-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm
docker-latest-logrotate-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm docker-latest-vim-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm
docker-latest-novolume-plugin-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm docker-latest-zsh-completion-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm
[root@b00c0ce22e3f docker-latest]# atomic-pkglayer *.rpm
Traceback (most recent call last):
File "/usr/bin/atomic-pkglayer", line 80, in <module>
sysroot.load(None)
GLib.Error: g-io-error-quark: openat: No such file or directory (1)
Expected results:
can successfully install RPM packages by atomic-pkglayer
Additional info:
If you run into issues with pkglayer, honestly I would just do:
mkdir -p /var/tmp/overlay/{work,upper}
mount -o remount,rw /usr
mount -t overlay overlayfs -o lowerdir=/usr,upperdir=/var/tmp/overlay/upper,workdir=/var/tmp/overlay/work /usr
That's basically what "ostree admin unlock" is doing at the core.
We've come a long way since this bug was open! atomic-pkglayer is no longer supported since rpm-ostree now supports package layering natively. Also note that the latest RHEL AH should already have docker-latest installed.
Description of problem: I can't use atomic-pkglayer to install docker-latest related RPM packages on Atomic Host, and got "GLib.Error: g-io-error-quark: openat: No such file or directory (1)" Version-Release number of selected component (if applicable): registry.access.redhat.com/rhel7/rhel-tools:latest (3b7bd2d69242) [cloud-user@atomic-00 ~]$ rpm -q docker atomic docker-1.9.1-26.el7.x86_64 atomic-1.9-4.gitff44c6a.el7.x86_64 How reproducible: always Steps to Reproduce: 1. docker pull registry.access.redhat.com/rhel7/rhel-tools 2. docker run -it registry.access.redhat.com/rhel7/rhel-tools:latest 3. download docker-latest related RPM packages in rhel-tools container 4. using atomic-pkglayer to install these RPM packages Actual results: [root@b00c0ce22e3f docker-latest]# ls docker-latest-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm docker-latest-selinux-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm docker-latest-fish-completion-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm docker-latest-utils-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm docker-latest-forward-journald-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm docker-latest-v1.10-migrator-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm docker-latest-logrotate-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm docker-latest-vim-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm docker-latest-novolume-plugin-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm docker-latest-zsh-completion-1.10.3-5.gitf8a9a2a.el7.x86_64.rpm [root@b00c0ce22e3f docker-latest]# atomic-pkglayer *.rpm Traceback (most recent call last): File "/usr/bin/atomic-pkglayer", line 80, in <module> sysroot.load(None) GLib.Error: g-io-error-quark: openat: No such file or directory (1) Expected results: can successfully install RPM packages by atomic-pkglayer Additional info: