The Subscription Manager package provides programs and libraries to allow users to manage subscriptions and yum repositories from the Candlepin.
- http://candlepinproject.org/
- https://fedorahosted.org/subscription-manager/
- https://github.com/candlepin/subscription-Manager
vagrant up can be used to spin up various VMs set up for development work.
These VMs are all configured using the included ansible role "subman-devel".
The PYTHONPATH and PATH inside these environments is modified so that
running subscription-manager or subscription-manager-gui will use
scripts and modules from the source code.
Currently, the source is set up as a vagrant shared folder using rsync. This
means that it is necessary to use vagrant rsync to sync changes with the
host if desired.
The ansible role that provisions the VMs tries to find the IP address of
candlepin.example.com, so if the candlepin vagrant image is started first,
then the box can resolve it. (If it is started later, vagrant provision can
be used to update the VM's hosts file).
Additionally, the Vagrantfile is set up for sharing base VMs with
katello/forklift. Specifically,
forklift plugins can be added to a subscription-manager checkout beneath
vagrant/pluginsin order to provide additional base images.
If RHEL-based images are added, then the Vagrantfile uses the values of
SUBMAN_RHSM_USERNAME, SUBMAN_RHSM_PASSWORD, SUBMAN_RHSM_HOSTNAME,
SUBMAN_RHSM_PORT, and SUBMAN_RHSM_INSECURE to register and auto-attach
during provisioning (best done in .bashrc or similar). If unspecified,
hostname and port are left alone (i.e. whatever is in the VM's rhsm.conf will
be untouched).
To register against subscription.rhsm.redhat.com, .bashrc might contain:
export SUBMAN_RHSM_USERNAME=foobar
export SUBMAN_RHSM_PASSWORD=password(Replace username and password with actual values).
To register against a local candlepin instance, .bashrc might contain:
export SUBMAN_RHSM_HOSTNAME=candlepin.example.com
export SUBMAN_RHSM_PORT=443
export SUBMAN_RHSM_INSECURE=1
export SUBMAN_RHSM_USERNAME=foobar
export SUBMAN_RHSM_PASSWORD=password(Replace username and password with actual values).
Note, however, since the registration is necessary to download RPMs to set up the VM for development, registering against a local candlepin might not be particularly useful (at least not for initial provisioning).
If you are working inside one of the vagrant boxes and you find subscription-manager and/or subscription-manager-gui will not work with output that looks like the following: "Unable to find Subscription Manager module. Error: libssl.so.10: cannot open shared object file: No such file or directory"
You should be able to run vagrant provision [vm-name] from the host machine to fix the issue.
This issue can happen if the python-rhsm/build or python-rhsm/build_ext directories are copied to the virtual machine and the virtual machine provides different libraries than those available on the build host.