Satellite 6 => OS release version not attached to a copied Activation Key correctly

Currently there seems to be a bug in Satellite 6 (6.1.6). I`ve created an Activation Key and attached a “Release Version” on the Details tab to the Activation Key. I also configured all other needed things like product content, subscriptions and so on.

If I now copy this Activation Key the Release Version seems to be present at the copied Activation Key. But when I try to install a new client with the copied Activation Key which for example has 7.2 as a release version then the client does not configure the release version via subscription-manager correctly during provisioning. This leads to the problem that the client is not able to access the correct RHEL Yum repositories on Satellite.

If I open the copied Activation Key again, delete the release version and attach the release version again, then the client can successfully access all needed Yum repositories with this specific release version during provisioning.

I filled an appropriate BZ entry (BZ 1311846).

Satellite 6 => Configure multiple network cards with static IP’s during host provisioning on VMWare

Satellite 6 offers the possibility to provision a host with multiple network cards, however an issue is faced when using VMWare in conjuction with Satellite 6 and you want to provision multiple network interfaces with static IP addresses.

What happens is that after the provisioning of a virtual machine is complete, multiple network cards are added, but only the primary interface (which is used for PXE / DHCP during installation) is configured correctly.

I created a workaround to get this working. I described this solution in an official Red Hat KCS article which is now verified by Red Hat Engineering and published to the public. You can find this article here.

Satellite 6 and Microsoft DNS integration

If you plan to deploy RHEL guests with Satellite 6 and your DNS server of choice is Microsoft DNS than Satellite 6 is also able to create / delete appropriate DNS entries for newly created hosts automatically via foremen-proxy on Microsoft DNS. This article describes on how to configure both Satellite 6 and Microsoft DNS.

Satellite 6 client bootstrap script

I have created a Python script which automatically registers your existing RHEL clients to a Satellite 6 / Katello 2 server or Capsule. It also configures your Puppet agent, creates a “Host” entry in Satellite 6 / Katello 2 Web-UI and starts an initial Puppet run. All you need to do is to sign the Puppet agent cert request on your Satellite or Capsule server (if autosign is not configured which is default).

You can run the script either interactively (The script searches all needed values on your Satellite and shows the findings as options. Currently you have to copy/paste the values.) or unattended (where you have to pass by ALL needed values like organization, location, hostgroup etc.).

You can find the script on Github: https://github.com/hambuergaer/sat6_client_configuration