Description of problem: Matcher value and puppet default can be set as matcher value for smart class parameter and at-a time. Actually If 'Use-puppet-default' option is checked for matcher, matcher value cannot be set from UI. And same is expected in CLI. Version-Release number of selected component (if applicable): foreman-1.11.0-0.develop.201602171602gitd5b5059.el7.noarch How reproducible: Always Steps to Reproduce: 1. Attempt to create matcher with override value and puppet default value at a time from CLI. # hammer -u admin -p changeme sc-param add-override-value --match <match> --value <value> --use-puppet-default 1 Actual results: Success! Both value and puppet default is set. Expected results: Either one is value is set -or- exception raised for wrong attempt. Additional info:
Upstream bug component is Provisioning
Upstream bug component is Hammer
Moving to POST since upstream bug http://projects.theforeman.org/issues/13832 has been closed
Verified in Sat 6.3 snap 8 ~]# hammer sc-param add-override-value --match os=* --value false --smart-class-parameter-id 202 --use-puppet-default 1 Could not create the override value: Error: Cannot use --value when --use-puppet-default is true See: 'hammer sc-param add-override-value --help'
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-2018:0336