Description of problem: When using a nonexistent repo name in a command, Hammer says: """ Error: No such repository with name , in lifecycle environment and content view """ There is obviously some text missing (entered repo name) Version-Release number of selected component (if applicable): Tested on Sat 6.4 snap 5 How reproducible: Deterministic Steps to Reproduce: # hammer host create --compute-resource-id 1 --architecture x86_64 --domain example.com --operatingsystem-id 1 --partition-table-id 1 --location-id 2 --organization-id 1 --name fishy --root-password toortoor --kickstart-repository 'NONEXISTENT_REPO' --lifecycle-environment-id 1 --content-view-id 1 Could not create the host: Error: No such repository with name , in lifecycle environment and content view Actual results: Missing entered repo name Expected results: Error: No such repository with name NONEXISTENT_REPO, in lifecycle environment and content view
upstream fix is merged: https://github.com/Katello/hammer-cli-katello/pull/561
Connecting redmine issue https://projects.theforeman.org/issues/23872 from this bug
rabajaj can you please check the upstream issue as to why it is not moved to fixed?
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/23872 has been resolved.
The fix for this is merged upstream and is in the latest 6.5 SNAP.
Verified with Sat 6.5 snap 7 # hammer host create --compute-resource-id 1 --architecture x86_64 --domain example.com --operatingsystem-id 1 --partition-table-id 1 --location-id 2 --organization-id 1 --name fishy --root-password toortoor --kickstart-repository 'NONEXISTENT_REPO' --lifecycle-environment-id 1 --content-view-id 1 Could not create the host: Error: No such repository with name NONEXISTENT_REPO, in lifecycle environment 1 and content view 1
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/RHSA-2019:1222
Clearing out the needinfo since the issue was resolved :)