Bug 1300460

Summary: Default parameter value still in YAML, even when "Use Puppet Default" is selected
Product: Red Hat Satellite Reporter: Maxim Burgerhout <mburgerh>
Component: Configuration ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.5CC: orabin
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-31 14:23:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Maxim Burgerhout 2016-01-20 22:16:31 UTC 
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:
Comment 1 Bryan Kearney 2016-07-26 19:06:32 UTC 
Moving 6.2 bugs out to sat-backlog.