Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
Overriding a puppet class with a smart class variable based on a boolean validation fails.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
Expect to see the smart class variable be honored for boolean = false to not run a specific puppet configuration change to the resolv.conf file based on the matcher value name ~ ls* however the client data json shows that it is being set to true still for that specific host even thought the Name value is correct in the json.
system.pp:
if $enable_resolv_conf {
file { '/etc/resolv.conf':
ensure => file,
mode => '0640',
owner => 'root',
group => 'root',
content => template('c2s/resolv.conf.erb'),
}
}
init.pp:
$enable_resolv_conf = $c2s::params::enable_resolv_conf,
validate_bool($enable_resolv_conf)
params.pp:
$enable_resolv_conf = true
Smart Variable set to boolean, default value true using puppet default, and matcher name ~ ls* set to false.
Actual results:
Expected results:
Wildcard to be honored
Description of problem: Overriding a puppet class with a smart class variable based on a boolean validation fails. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: Expect to see the smart class variable be honored for boolean = false to not run a specific puppet configuration change to the resolv.conf file based on the matcher value name ~ ls* however the client data json shows that it is being set to true still for that specific host even thought the Name value is correct in the json. system.pp: if $enable_resolv_conf { file { '/etc/resolv.conf': ensure => file, mode => '0640', owner => 'root', group => 'root', content => template('c2s/resolv.conf.erb'), } } init.pp: $enable_resolv_conf = $c2s::params::enable_resolv_conf, validate_bool($enable_resolv_conf) params.pp: $enable_resolv_conf = true Smart Variable set to boolean, default value true using puppet default, and matcher name ~ ls* set to false. Actual results: Expected results: Wildcard to be honored