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).
Comments are closed.