Description of problem:
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.
Version-Release number of selected component (if applicable):
- Satellite 6.1.6
- RHEL 7.2
- Copy an Activation Key with "Release Version" configured.
Steps to Reproduce:
1. Copy an Activation Key with "Release Version" configured.
2. Do not change anything regarding "Release Version"
The release version seems to be configured at the copied Activation Key without taking effect.
If an activation key will be copied then I expect every parameter configured at the parent activation key will also be configured correctly at the copied activation key without any manual interventions.
Moving 6.2 bugs out to sat-backlog.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.