Forge Home


rhnreg_ks provider for Puppet


1,336,415 latest version

4.6 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.1.3 (latest)
  • 0.1.2
  • 0.1.1
  • 0.1.0 (deleted)
  • 0.0.1 (deleted)
released Oct 21st 2016
This version is compatible with:

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'strider-rhnreg_ks', '0.1.3'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add strider-rhnreg_ks
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install strider-rhnreg_ks --version 0.1.3

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



strider/rhnreg_ks — version 0.1.3 Oct 21st 2016


This module provides Custom Puppet Providers to handle Red Hat Network Registering and subscribing to additional channels. It works with RHN or a Red Hat Network Satellite Server.


Read Licence file for more information.



  • Gaël Chamoulaud (gchamoul at redhat dot com)

Types and Providers

The module adds the following new types:

  • rhn_register for managing Red Hat Network Registering
  • rhn_channel for adding/removing channels



  • activationkeys: The activation key to use when registering the system (cannot be used with username and password)
  • ensure: Valid values are present, absent. Default value is present.
  • force: Should the registration be forced. Use this option with caution, setting it true will cause the rhnreg_ks command to be run every time runs. Default value false.
  • force_check: Should the registration be forced if the server_url on the current system has a mismatch with the one defined during the puppet run. Default value false.
  • hardware: Whether or not the hardware information should be probed. Default value is true.
  • packages: Whether or not packages information should be probed. Default value is true.
  • password: The password to use when registering the system
  • profile_name: The name the system should use in RHN or Satellite
  • proxy: If needed, specify the HTTP Proxy
  • proxy_password: Specify a password to use with an authenticated http proxy
  • proxy_user: Specify a username to use with an authenticated http proxy
  • rhnsd: Whether or not rhnsd should be started after registering. Default value is true.
  • server_url: Specify a url to use as a server
  • ssl_ca_cert: Specify a file to use as the ssl CA cert
  • username: The username to use when registering the system
  • virtinfo: Whether or not virtualiztion information should be uploaded. Default value is true.


  • channel The channel to manage. (This is the namevar).
  • ensure Valid values are present, absent.
  • username The username to use when adding/removing a channel.
  • password The password to use when adding/removing a channel.


Registering Clients to Red Hat Network RHN Satellite Server:

Registering Clients to RHN Server:

Adding a Channel:


In your puppet modules directory:

git clone

Ensure the module is present in your puppetmaster's own environment (it doesn't have to use it) and that the master has pluginsync enabled. Run the agent on the puppetmaster to cause the custom types to be synced to its local libdir (puppet master --configprint libdir) and then restart the puppetmaster so it loads them.


Please file any issues or suggestions on on GitHub