Bug 1737497

Summary: hammer docker --help returns ERROR output
Product: Red Hat Satellite Reporter: Sergei Petrosian <spetrosi>
Component: HammerAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: vijsingh
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: apatel, kgaikwad, mbacovsk, mshira, ofedoren, rabajaj
Target Milestone: Unspecified   
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-08-08 09:08:47 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: 1737463    

Description Sergei Petrosian 2019-08-05 14:07:07 UTC 
Description of problem:

The `hammer docker --help` command returns Error output:
~~~~~~
# hammer docker --help
Error: uninitialized constant HammerCLIKatello::LifecycleEnvironmentNameResolvable
Did you mean?  HammerCLIKatello::LifecycleEnvironmentNameMapping
~~~~~~

This causes the more serious problem: I cannot get the full output from the "hammer full-help" command as it finishes with the same output.

Version-Release number of selected component (if applicable):
# rpm -q satellite
satellite-6.6.0-5.beta.el7sat.noarch

How reproducible:
Always


Steps to Reproduce:
1. Run hammer docker --help
2. Or run hammer full-help

Actual results:
Successful output

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

Additional info:
This issue is urgent for Satellite Docs because we are using the output of `hammer full-help --md` to generate the Hammer CLI guide. The new version of Hammer reference must be generated before the beta release.
Comment 3 Sergei Petrosian 2019-08-08 09:08:47 UTC 
This somehow works for me on the latest snap.
Comment 4 Martin Bacovsky 2019-08-08 12:18:17 UTC 
This should be already fixed in latest snap. Closing as a duplicate.

*** This bug has been marked as a duplicate of bug 1730026 ***