Description of problem: When editing a host group, changing the life cycle environment automatically unsets the Media and Partition Table fields under the Operating System tab. The 'PXE loader' field also changes to a different value from the one set originally. Version-Release number of selected component (if applicable): Satellite 6.9.1 How reproducible: 100% Steps to Reproduce: 1. Create host group [Host Group] tab Host group: <hgtest> Life cycle environment: <lcetest> Content View: <ccvrhel8> Content Source: <satellite.example.org> [Network] Domain: <example.org> IPv4 Subnet: <mysubnet> [Operating System] Architecture: x86_64 Operating System: RedHat 8.3 Media selection: All Media Media: <RHEL83UEFI> Partition Table: Kickstart default PXE loader: PXELinux UEFI [Locations] and [Organisations] mylocation myorg 2. Edit 'hgtest' and change the Lifecycle Environment field to a different value. Note: the Content View field becomes unset so remember to set it back. [Host Group] tab Life cycle environment: <lceprod> Content View: <ccvrhel8> 3. Before submitting the above change, check the [Operating System] tab. Actual results: [Operating System] tab Media: (blank) Partition Table: (blank) PXE loader: PXELinux BIOS Expected results: Changing the Lifecycle Environment field should not unset the Media and Partition Table fields. The PXE loader field should not change to a different type without warning. Additional info: - Already checked that Operating system 'RedHat 8.3' is associated with partition table 'kickstart default' and Installation Media 'RHEL8.3'. - If PXE loader is set to (None), it changes to 'PXELinux BIOS'. - Synced media is intentionally not used.
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36278 has been resolved.
Tested in 6.14. snap 5 (foreman-3.7.0-2.el8sat.noarch). Following the reproducer from comment 0, the Media and Partition Table values don't change after changing the Lifecycle Environment of the host group. Which is good news. However, after changing the Lifecycle Environment, the "PXE loader" value is always set to "PXELinux BIOS", regardless what value you have set there before. The same behavior is reproduced in the 6.13 clone bug 2211961. @Adam, I have the 6.14 & 6.13 environments, if you want to check it and then we can agree upon the next steps, i.e., if to verify this and file a follow-up bug just for the PXE loader issue or if to move this bug to ASSIGNED.
After talking to @aruzicka , failing the BZ due to the residual problem mentioned in my previous comment 21 - ..."PXE loader" value is always set to "PXELinux BIOS", regardless what value you have set there before. FailedQA in foreman-3.7.0-2.el8sat.noarch (6.14 snap 5).
https://github.com/theforeman/foreman/pull/9767 was merged in upstream