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 1228167 - "Atomic" `labels` variable has no command keyword
Summary: "Atomic" `labels` variable has no command keyword
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: Luwen Su
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-04 10:36 UTC by Luwen Su
Modified: 2019-03-06 01:14 UTC (History)
4 users (show)

Fixed In Version: docker-1.6.2-8.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-23 09:30:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1167 0 normal SHIPPED_LIVE docker bug fix update 2015-06-23 13:29:05 UTC

Description Luwen Su 2015-06-04 10:36:28 UTC
Description of problem:
Execute `atomic run $image` or any commands need call `def _get_args(self, label)` will trigger a key error.


Version-Release number of selected component (if applicable):
docker-1.6.2-6.el7.x86_64
atomic-0-0.32.git2f1398c.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Prepare a valid image
# atomic version rhel7
65de4a13fc7cf28b4376e65efa31c5c3805e18da4eb01ad0c8b8801f4a10bc16 redhat/rhel7-7.1-6 registry.access.redhat.com/rhel7:latest

2.# atomic run rhel7
Traceback (most recent call last):
  File "/usr/bin/atomic", line 188, in <module>
    sys.exit(args.func())
  File "/usr/lib/python2.7/site-packages/Atomic/atomic.py", line 326, in run
    args = self._get_args("RUN")
  File "/usr/lib/python2.7/site-packages/Atomic/atomic.py", line 264, in _get_args
    return labels[l].split()
KeyError: 'RUN'

3.
The `labels` has no command key word
{u'Vendor': u'Red Hat, Inc.', u'Name': u'redhat/rhel7', u'Build_Host': u'rcm-img05.build.eng.bos.redhat.com', u'Version': u'7.1', u'Architecture': u'x86_64', u'Release': u'6', u'BZComponent': u'rhel-server-docker', u'Authoritative_Registry': u'registry.access.redhat.com'}

Comment 2 Luwen Su 2015-06-04 10:50:37 UTC
Found the patch 
https://github.com/projectatomic/atomic/commit/3e96d72a66c92f70e99fa087e9115aba4d71bc9a, wait for the next build

Comment 3 Daniel Walsh 2015-06-04 12:10:30 UTC
Lokesh, I checked in a fix for this last night.  Please create a new docker build.

Comment 5 Luwen Su 2015-06-15 08:31:54 UTC
In docker-1.6.2-10.el7.x86_64, atomic-0-0.36.gitf863afd.el7.x86_64 it works for me

Comment 7 errata-xmlrpc 2015-06-23 09:30:16 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-2015-1167.html


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