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.

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