Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html-single/Puppet_Guide/index.html#sect-Red_Hat_Satellite-Puppet_Guide-Building_Puppet_Modules_from_Scratch-Generating_a_New_Module_Boilerplate Section Number and Name: section 3.7 "Configuring Smart Variables from Puppet Classes" Describe the issue: The Puppet guide seems to have a consistency issue in the section referring to building your own class and configuring smart variables. In section 3.7 the comment is: For example, mymodule contains a parameter for the HTTP port of our web server. This parameter, httpd_port, is set to a default of 8120. Except the mymodule class that is built in the tutorial doesn't include an httpd_port parameter. There is an httpd_port variable referenced in the template and in the SELinux rule, but it's not a parameter with a default value in the mymodule class. From section 2.9 of the same document (no parameter in mymodule class declaration) class mymodule { include mymodule::httpd include mymodule::app } I also believe the way the firewall and SELinux exec resources are configured in the example mymodule is likely to cause problems. They are both subscribed to the httpd package resource and are configured for refresh only, so will only fire/execute if the httpd package resource changes. If the httpd package is already installed on the server Puppet won't change the state of the httpd package resource, so I don't believe it will execute these Execs. Additionally, if you run the module and it configures the port (say 8120) and you then change the port and re-run Puppet, the firewall and iptables Exec won't execute to update the port because the httpd package state won't change (it's already installed), so your saved firewall and SELinux configuration will be out of step with your passed in parameter. Apologies for formatting, there is currently something wrong with the discussion forum that is breaking formatting in responses. Suggestions for improvement: Additional information: Reported here: https://access.redhat.com/discussions/1987953#comment-994313
PixelDrift.NET Support wrote: To follow up on the 'mymodule' example Puppet module problems, here is an example of the issue. I have created a basic manifest to run locally that triggers an exec in the same way as the sample module (httpd_port variable provided inline rather than a parameter, but same outcome). $httpd_port = 4000 package { "httpd": ensure => installed, } exec { "firewall-cmd ${httpd_port}": command => "/bin/echo \"this message in place of iptables\"", refreshonly => true, subscribe => Package['httpd'], } Results from the first run are in the below code block. httpd is installed and exec fires because state of 'httpd' package changes from not installed to installed. [root@cupcake ~]# puppet apply mymodule.pp Notice: Compiled catalog for cupcake.pixeldrift.local in environment production in 0.40 seconds Notice: /Stage[main]/Main/Package[httpd]/ensure: created Notice: /Stage[main]/Main/Exec[firewall-cmd 4000]: Triggered 'refresh' from 1 events Notice: Finished catalog run in 10.15 seconds Now that the package is installed, the Exec will no longer fire, so the firewall port will never be updated. To demonstrate this, you can change the httpd_port variable at the start of the mymodule.pp file, eg. $httpd_port = 3000 Now when you re-run the script the Exec (firewall) update won't occur because the httpd package is already installed even though the variable/parameter has changed. [root@cupcake ~]# puppet apply mymodule.pp Notice: Compiled catalog for cupcake.pixeldrift.local in environment production in 0.39 seconds Notice: Finished catalog run in 0.53 seconds This problem exists for both the firewall and semanage commands in the example mymodule Puppet module. I think the example needs reworking. --------------------------- Source: https://access.redhat.com/discussions/1987953#comment-994733
Hello These changes are now live on the customer portal. For 6.1 https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html-single/Puppet_Guide/index.html#sect-Red_Hat_Satellite-Puppet_Guide-Building_Puppet_Modules_from_Scratch-Configuring_the_HTTP_Server For 6.2 https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/puppet-guide/26-configuring-the-http-server Thank you
*** Bug 1273743 has been marked as a duplicate of this bug. ***