Description of problem: With hammer CLI trying to get sc-params details of hostgroup fails with error "missing param hostgroup_id' in parameters" when trying using options --hostgroup and --hostgroup-id. Version-Release number of selected component (if applicable): rubygem-hammer_cli-0.1.4.13-1.el7sat.noarch How reproducible: Always Steps to Reproduce: 1. Try to get sc-params of hostgroup using hammer CLI. # hammer hostgroup sc-params --hostgroup <hostgroup-name> --hostgroup-id <hostgroup-id> missing param 'hostgroup_id' in parameters 2. --hostgroup-id option do not work with --name too. # hammer hostgroup sc-params --name <hostgroup-name> --hostgroup-id <hostgroup-id> Error: 400 Bad Request 3. It do not work alone too as like --id option. # hammer hostgroup sc-params --hostgroup-id <hostgroup-id> missing param 'hostgroup_id' in parameters Actual results: missing param 'hostgroup_id' in parameters Error: 400 Bad Request Expected results: It should work as like --id option. Additional info:
Created redmine issue http://projects.theforeman.org/issues/13995 from this bug
Upstream bug component is Provisioning
Based on the comment on the upstream redmine, I am moving this to ON_QA for verification against Satellite 6.2.
Verified this in Sat 6.2 snap 8.1. The issue is no more reproducible. All the said commands in Description are working as expected. 1. hammer hostgroup sc-params --hostgroup hg1 --hostgroup-id 1 ---|-----------|---------------|----------|------------- ID | PARAMETER | DEFAULT VALUE | OVERRIDE | PUPPET CLASS ---|-----------|---------------|----------|------------- 2. hammer hostgroup sc-params --name hg1 --hostgroup-id 1 Error: Unrecognised option '--name' 3. hammer hostgroup sc-params --hostgroup-id 1 ---|-----------|---------------|----------|------------- ID | PARAMETER | DEFAULT VALUE | OVERRIDE | PUPPET CLASS ---|-----------|---------------|----------|------------- Only the second command having --name option is not testable as --name option is removed from listing hostgroup sc-params from hammer. So moving to verified.
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:1500