Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1730026

Summary: Some hammer docker commands fail with uninitialized constant HammerCLIKatello::LifecycleEnvironmentNameResolvable
Product: Red Hat Satellite Reporter: Mirek Długosz <mzalewsk>
Component: Hammer - ContentAssignee: Martin Bacovsky <mbacovsk>
Status: CLOSED ERRATA QA Contact: Peter Dragun <pdragun>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: apatel, kgaikwad, mbacovsk, mshira, ofedoren, rabajaj, spetrosi
Target Milestone: 6.6.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 13:30:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1713222, 1737463    

Description Mirek Długosz 2019-07-15 15:41:35 UTC
Some hammer commands fail with:

Error: uninitialized constant HammerCLIKatello::LifecycleEnvironmentNameResolvable
Did you mean?  HammerCLIKatello::LifecycleEnvironmentNameMapping


This definitely happens on `hammer docker manifest list`, but I am yet to discover full scope of the problem.


Version:
Satellite 6.6.0 snap 11
pulp-server-2.19.1-1.el7sat.noarch
satellite-6.6.0-5.beta.el7sat.noarch
katello-3.12.0-1.el7sat.noarch
foreman-1.22.0.9-1.el7sat.noarch
tfm-rubygem-hammer_cli_katello-0.18.0.2-1.el7sat.noarch
tfm-rubygem-hammer_cli-0.17.1-2.el7sat.noarch

Comment 3 Martin Bacovsky 2019-07-23 22:52:12 UTC
Created redmine issue https://projects.theforeman.org/issues/27397 from this bug

Comment 4 Martin Bacovsky 2019-07-23 23:17:01 UTC
It seems only 'hammer docker manifest list' and 'hammer docker tag list` commands are affected

Comment 5 Bryan Kearney 2019-07-24 00:02:19 UTC
Upstream bug assigned to mbacovsk

Comment 6 Bryan Kearney 2019-07-24 10:02:10 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27397 has been resolved.

Comment 7 Martin Bacovsky 2019-07-26 16:55:29 UTC
Moving to ON_QA as the related patch was included in Snap 13

Comment 8 Martin Bacovsky 2019-08-08 12:18:17 UTC
*** Bug 1737497 has been marked as a duplicate of this bug. ***

Comment 9 Peter Dragun 2019-08-29 09:18:00 UTC
Verified on Sat 6.6 snap 17. Using commands 'hammer docker manifest list' and 'hammer docker tag list'. Both ended without error.

Comment 11 errata-xmlrpc 2019-10-22 13:30:45 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-2019:3175