Project

General

Profile

Actions

Bug #12878

closed

Default Puppet parameter from Satellite is still validated if "Use Puppet default" is selected

Added by Bryan Kearney almost 9 years ago. Updated almost 9 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1229404
Description of problem:
If "Use Puppet default" is selected, the value that is inserted as the default from Satellite 6, will never be used. Even though, it is still validated for parameter type.

This breaks when, for example, you use a module that uses an array parameter from a params.pp file like '"${$::class::params::var'}".

Setting 'parameter type' to array will break because the 'Default value' "${$::class::params::var}" parses as a string, but you cannot set it to 'string', because that will break merging of overrides.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. install puppetlabs-ntp
2. check 'override', check 'use puppet default' and set parameter type to 'array'
3. try and override the value somewhere

Actual results:
you actually cannot even save the parameter setup, because Sat6 will tell you "Value to use when there is no match is invalid", as it is a string, and not an array

Expected results:
value of 'default value' is ignored for validation if 'use puppet default' is checked

Additional info:


Related issues 1 (0 open1 closed)

Is duplicate of Foreman - Bug #9187: Overrideable empty puppet class parameters are still validate their default valueClosedOri Rabin02/02/2015Actions
Actions #1

Updated by Dominic Cleal almost 9 years ago

  • Is duplicate of Bug #9187: Overrideable empty puppet class parameters are still validate their default value added
Actions #2

Updated by Dominic Cleal almost 9 years ago

  • Status changed from New to Duplicate
Actions

Also available in: Atom PDF