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 1317367 - Respin of 7.2.3 rhel-tools-docker
Summary: Respin of 7.2.3 rhel-tools-docker
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rhel-tools-container
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Eliska Slobodova
QA Contact: atomic-bugs@redhat.com
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks: 1357094
TreeView+ depends on / blocked
 
Reported: 2016-03-14 06:41 UTC by Frantisek Kluknavsky
Modified: 2023-09-14 03:19 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1313030
: 1357094 (view as bug list)
Environment:
Last Closed: 2016-03-31 23:26:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0578 0 normal SHIPPED_LIVE Red Hat Enterprise Linux Atomic Tools Container Image Update 2016-04-01 03:21:43 UTC

Description Frantisek Kluknavsky 2016-03-14 06:41:34 UTC 
Tracking the respin of rhel-tools-docker
Comment 6 Daniel Walsh 2016-03-22 15:42:47 UTC 
Looks like you are trying to install an rpm package onto an atomic host?
Comment 7 Colin Walters 2016-03-22 15:50:40 UTC 
This is an incompatiblity with atomic-pkglayer and the docker `%post` - it's unaware that we're running inside a container.

https://github.com/GNOME/ostree/pull/212

will address this by allowing use of `rpm -Uvh docker.rpm` outside of a container.
Comment 8 Colin Walters 2016-03-22 15:52:16 UTC 
Currently though in order to test the new Docker you'd need an updated tree.

We can probably fix this in docker though by having its %post detect if it's inside a container and not try to load the policy?  Something like `if test ${container} = "docker"` ?
Comment 9 Daniel Walsh 2016-03-22 15:54:43 UTC 
It is actually blowing up when trying to compile policy.
Comment 10 Alex Jia 2016-03-22 16:05:40 UTC 
(In reply to Daniel Walsh from comment #6)
> Looks like you are trying to install an rpm package onto an atomic host?

Yes, using atomic-pkglayer to update docker RPM pacakges onto an      Atomic Host.
Comment 11 Alex Jia 2016-03-24 09:06:22 UTC 
(In reply to Colin Walters from comment #8)
> We can probably fix this in docker though by having its %post detect if it's
> inside a container and not try to load the policy?  Something like `if test
> ${container} = "docker"` ?

Colin, do we plan to fix this on 7.2.4? if so, I will close the bug as VERIFIED, because except this failure, the atomic-pkglayer works well.
Comment 13 errata-xmlrpc 2016-03-31 23:26:54 UTC 
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, 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://rhn.redhat.com/errata/RHBA-2016-0578.html
Comment 14 Red Hat Bugzilla 2023-09-14 03:19:22 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.