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.

When unchecking the override checkbox the matchers and validators are saved so when it's checked again they are all there.
All the checkboxes on the form (use puppet default, hidden value, required) are unchecked (because they are disabled and don't send their value).
This should be consistent - we either save the state of the parameter or we remove everything.

Created from redmine issue http://projects.theforeman.org/issues/13976

Upstream bug assigned to orabin

upstream bug is merged

Moving to POST since upstream bug http://projects.theforeman.org/issues/13976 has been closed
-------------
Ori Rabin
Applied in changeset commit:dba5afe0f39748ea8dafad88a7da046a6aab5c9a.

Verified this in Sat 6.2 snap 8.1

I see that on unchecking the override parameter, all other entities(checkboxes, values) state is saved.

I am agree with this update and its one of the solution suggested in Description of bug.

So moving this to Verifed.

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