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:
I have a class that I assigned a default value to from Satellite. When I checked the "Use Puppet Default" box for a specific host, the value from Satellite remained listed in the YAML output, so the Puppet default was never used.

Version-Release number of selected component (if applicable):
foreman-1.7.2.49-1.el7sat.noarch
puppet-3.6.2-4.el7sat.noarch

How reproducible:


Steps to Reproduce:
1. Add a class to Satellite, override one of it's values and give it a default
2. For a specific host, override that value and check "Use Puppet Default"
3.

Actual results:
Default value from Satellite is still in the YAML output

Expected results:
Default value from Satellite is no longer listed in the YAML output

Additional info:

Moving 6.2 bugs out to sat-backlog.