Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
In the Content Management (RedHat Repositories, ActivationKey, ContentHost) you can select 6Server/7Server as release_version.
The Provisioning side (Foreman) does not have corresponding entries in the Operatingsystems. This makes it complex to associate the correct OS entry for hosts that are bound to 6Server/7Server (e.g. the Satellite host itself must be on 6Server/7Server as it does not support EUS/Zstream)
Secondly there is no Kickstart repository for 6Server/7Server available, that makes it strange to select a 6.x/7.x for Kickstart repository and then 6Server/7Server for the other repositories
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Sync 6Server repos
2. Create Contentview with 6Server repos and 6Server Kickstart
3. Create Activation Key with 6Server as release
4. Create Host in Foreman with the Activation Key
5. Associate OS
Actual results:
- In step 2 the Kickstart repository of 6Server is not available
- In step 5 Inconsistent behaviour and associations between Operatingsystem and release version
Expected results:
Consistent behaviour RedHat version names in:
- Kickstart
- Release_version
- Operating systems
It might come handy to have in two variables with the OS version:
- Target OS release to for Content/Provision
- Actual running OS release
These might be different and it is good to know if those are out-of-sync, because then the yum update command still has to be run
Additional info:
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the 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.