Bug 1300460 - Default parameter value still in YAML, even when "Use Puppet Default" is selected
Summary: Default parameter value still in YAML, even when "Use Puppet Default" is sele...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Configuration Management
Version: 6.1.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-20 22:16 UTC by Maxim Burgerhout
Modified: 2019-09-26 13:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-31 14:23:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 12249 0 None None None 2016-10-31 14:23:24 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.