Including resilient storage and HA packages during provisioning

Latest response

In Red Hat Satellite 6.1, I have a Content View that contains RHEL rpm repos, resilient storage repos and high availability repos. I am using an activation key that has a resilient storage subscription associated with it. I am provisioning some hosts and I have packages from resilient storage and HA repos included in the %packages section of my kickstart.
Auto-attach is enabled. After my hosts are provisioned, the extra packages are not installed. I am forced to go into the Satellite interface and add the resilient storage to each Content Host one by one. Then on the Content Host itself I run `subscription-manager refresh', then I am able to install the extra packages.
Is there a way to tie the subscription to the content host during the kickstart process to eliminate these manual steps?
Thanks,
Eric

EL
Log in to join the conversation

Responses

Rich Jerrido's picture Red Hat Guru 2300 points
31 May 2016 1:30 PM

On your activation key, do you have the 'auto-attach' value set to 'True'? If yes, then the behavior of your activation key becomes 'attach only the subscriptions that match my installed products (as listed in /etc/pki/product)'.

As you haven't installed any RPMs from the HA/RS repos (yet), you don't have those products installed and thus the auto-attach algorithm doesn't work. There are two ways to solve this:

Method 1: change the 'auto-attach' value on your activation key from 'True' to 'False' . An activation key with auto-attach set to False changes its behavior to 'Use EXACTLY the subscriptions specified'

Method 2: Red Hat Installation Media, if I remember correctly, include the HA & RS repos on the install media. This should allow you to install the packages at installation time (prior to the subscription-manager register invocation), which would also place the requisite product certificates into /etc/pki/product, which allows auto-attach to work correctly. (Note: I am doing this from memory, so I may have missed a step, but that is the gist of it) .

EL Community Member 92 points
10 June 2016 5:39 PM

Thank you Rich, after setting 'auto-attach' to false, the packages did not get installed when they were listed in the %packages section. What worked was setting 'auto-attach' to false then moving the installation of the extra packages to the %post section of the provisioning template by inserting a 'yum install' command to install them.

Rich Jerrido's picture Red Hat Guru 2300 points
16 June 2016 12:14 PM

That is correct and by design. It isn't until AFTER the subscription-manager register command that those repos are available. The %packages section of a kickstart can only use RPMs which are in the repositories specified via --url or --repo in the kickstart file.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.