Bug 2211961

Summary: When editing a host group, changing the life cycle environment automatically unsets the Media and Partition Table fields under the Operating System tab
Product: Red Hat Satellite Reporter: Odilon Sousa <osousa>
Component: Host GroupAssignee: Adam Ruzicka <aruzicka>
Status: CLOSED ERRATA QA Contact: Pavel Novotny <pnovotny>
Severity: high Docs Contact:
Priority: high    
Version: 6.9.0CC: ahumbe, aruzicka, inecas, kgaikwad, ldelouw, mkalyat, momran, oliver, pcreech, pdwyer, pnovotny, rdesouza, satellite6-bugs, vijsingh
Target Milestone: 6.13.2Keywords: Triaged, UserExperience
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-4.7.0.26-1,foreman-3.5.1.18-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1955046 Environment:
Last Closed: 2023-07-12 15:37:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 3 Pavel Novotny 2023-06-29 11:16:33 UTC 
Waiting for needinfo in the original 6.14 bug, see Bug #1955046 comment 21.
Comment 4 Pavel Novotny 2023-06-30 13:15:49 UTC 
After talking to @aruzicka , the resolution is that his bug is VERIFIED with foreman-3.5.1.18-1.el8sat.noarch (6.13.2 snap 2), in this scope:

By following the reproducer in comment 0, the "Media" and "Partition Table" fields do no longer unset and keep the currently set values.


However, after changing the Lifecycle Environment, the "PXE loader" value is always set to "PXELinux BIOS", regardless what value you have set there before.
This issue is now tracked as a separate bug 2218891.
Comment 13 errata-xmlrpc 2023-07-12 15:37:22 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Satellite 6.13.2 Async Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:4043