-
Bug
-
Resolution: Unresolved
-
Normal
-
6.16.5
-
False
-
sat-rocket
-
None
-
None
-
None
-
To Do
Description of problem:
When installing satellite, the default Operating System will be created, and it will be something like "RHEL", instead of "RedHat".
Let's assume that we deployed a server rhel9.3, and installed Satellite 6.16. This will create an Operating System called "RHEL 9.3", after sometime, when doing the update, the BaseOS got updated to 9.4, then a new Operating System will be created "RHEL9.4".
Now, if we go to the kickstart repositories, and enabled the BaseOS kickstart of 9.5, the Operating System "RedHat 9.5" will be created, and this is the expected.
Here is the problem, if I would like to enable the version 9.4, the system will use "RHEL 9.4", instead of creating a new Operating System, and this will reflect in all the systems, eventually, when registering Content Hosts of version 9.4
How reproducible:
100%
Is this issue a regression from an earlier version:
Steps to Reproduce:
1. Install Satellite and check the Operating Systems (it will be RHEL 9.6), assuming that you are installing Satellite on top of rhel9.6
2. Enable the kickstart of rhel9.6 BaseOS (the same "RHEL 9.6" will be used under your Operating System)
3. Enable the kickstart of rhel9.5 BaseOS (you will see "RedHat 9.5" under your Operating System)
Actual behavior:
Satellite is creating "RHEL" instead of "RedHat"
Expected behavior:
When installing Satellite, the default Operating System should be "RedHat" instead of "RHEL"
Business Impact / Additional info:
- is blocked by
-
SAT-39947 [SPIKE] come up with a recommendation for SAT-36540: duplicate OS & fact parsers
-
- In Progress
-
- is triggering
-
SAT-40641 Puppet fact parser can't create OS entry blocking Satellite leapp upgrades
-
- New
-
- relates to
-
SAT-19269 After a successful in-place upgrade of the satellite server to RHEL-9 using Leapp, Satellite GUI still shows the old/wrong Operating System version
-
- Closed
-
- links to