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 1331429 - atomic help crash with label
Summary: atomic help crash with label
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: atomic
Version: 7.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-28 13:48 UTC by Qian Cai
Modified: 2016-06-23 16:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-23 16:21:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1273 0 normal SHIPPED_LIVE atomic bug fix and enhancement update 2016-06-23 20:13:11 UTC

Description Qian Cai 2016-04-28 13:48:30 UTC
Description of problem:
# cat Dockerfile
FROM caiqian/centos:5
label HELP "iron man"

# atomic help baseimg
iron man
Traceback (most recent call last):
   File "/bin/atomic", line 525, in <module>
     sys.exit(_func())
   File "/usr/lib/python2.7/site-packages/Atomic/help.py", line 42, in help
     self.display_alt_help()
   File "/usr/lib/python2.7/site-packages/Atomic/help.py", line 94, in display_alt_help
     util.check_call(cmd, env=self.cmd_env())
   File "/usr/lib/python2.7/site-packages/Atomic/util.py", line 80, in check_call
     return subprocess.check_call(cmd, env=env, stderr=stderr, stdout=stdout)
   File "/usr/lib64/python2.7/subprocess.py", line 537, in check_call
     retcode = call(*popenargs, **kwargs)
   File "/usr/lib64/python2.7/subprocess.py", line 524, in call
     return Popen(*popenargs, **kwargs).wait()
   File "/usr/lib64/python2.7/subprocess.py", line 711, in __init__
     errread, errwrite)
   File "/usr/lib64/python2.7/subprocess.py", line 1327, in _execute_child
     raise child_exception
OSError: [Errno 2] No such file or directory

Version-Release number of selected component (if applicable):
# rpm -q docker atomic
docker-1.9.1-32.el7.x86_64
atomic-1.9-4.gitff44c6a.el7.x86_64

How reproducible:
always

Comment 1 Daniel Walsh 2016-04-28 13:51:24 UTC
Fixed in atomic-1.10.

Comment 4 Alex Jia 2016-06-11 14:55:30 UTC
I can reproduce the bug on atomic-1.9-4 and the latest atomic help can read HELP label and got expected string, so move the bug to VERIFIED status.

# rpm -q atomic docker 
atomic-1.10.3-2.el7.x86_64
docker-1.10.3-31.el7.x86_64

Comment 6 errata-xmlrpc 2016-06-23 16:21:38 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://access.redhat.com/errata/RHBA-2016:1273


Note You need to log in before you can comment on or make changes to this bug.