Forge Home


rhnreg_ks provider for Puppet


9,990 latest version

3.5 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.0.1 (latest)
released Jun 11th 2014

Start using this module

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

Add this module to your Puppetfile:

mod 'nohtyp-rhnreg_ks', '0.0.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

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

Manually install this module globally with Puppet module tool:

puppet module install nohtyp-rhnreg_ks --version 0.0.1

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.



nohtyp/rhnreg_ks — version 0.0.1 Jun 11th 2014


This module provides a custom puppet provider to handle RHN, SATELLITE and SPACEWALK server registering/un-registering. Also, module handles VMware cloning.


Read Licence file for more information.


Inspired by

Type and Provider

The module adds the following new types:

  • rhn_register for managing Red Hat Network Registering


  • activationkeys: The activation key to use when registering the system
  • ensure: Valid values are present, absent. Default value is present.
  • force: No need to use this option, unless want to register system every 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 (required)
  • profile_name: The name the system should use in RHN or Satellite(if not set defaults to hostname)
  • 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 (required)
  • ssl_ca_cert: Specify a file to use as the ssl CA cert
  • username: The username to use when registering the system (required)
  • virtinfo: Whether or not virtualiztion information should be uploaded. Default value is true.


Registering Clients to RHN Server with activation keys:

Un-register Clients RHN Server with activation keys:


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.


username and password are required to connect to the RHN, SATELLITE, SPACEWALK server to check if server previously exists.

In a normal configuration username/password and activationkeys could not be used together, but since this module will support RHN, SATELLITE, SPACEWALK register and un-register by being able to log into the system using the api it needs username/password.

To see the output of what the module is doing, run with the --debug option.


Please file any issues or suggestions on on GitHub