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:
This a separate bug for the leftover issue of bug 2211961:
When editing a host group, changing the life cycle environment automatically sets the "PXE loader" value to "PXELinux BIOS" on the Operating System tab.
Version-Release number of selected component (if applicable):
foreman-3.5.1.18-1.el8sat.noarch
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
PXE loader: PXELinux BIOS
Expected results:
PXE loader: PXELinux UEFI
Additional info:
After talking to @aruzicka , we decided to track the leftover issue in 6.13 bug 2211961 separately as this bug and it is meant to be fixed only in the 6.13 version!
Fixing the issue in 6.14+ is handled in bug 1955046
The same problem can be reproduced for both Hosts and Host Groups objects and with the change in any of the following i.e. Lifecycle, Content View, or Content Source.
I don't see the Loaders are inherited at all but they are always reset back to default "PXELinux BIOS" with every POST request on the Host or Hostgroup object and the OS is selected:
2024-03-25T15:12:41 [I|app|1c55f2dd] Started POST "/hostgroups/os_selected" for X.Y.X.Z at 2024-03-25 15:12:41 +0530
2024-03-25T15:12:41 [I|app|1c55f2dd] Processing by HostgroupsController#os_selected as */*
2024-03-25T15:12:41 [I|app|1c55f2dd] Parameters: {"hostgroup"=>{"operatingsystem_id"=>"2", "ptable_id"=>"", "medium_id"=>"", "lifecycle_environment_id"=>"5", "content_view_id"=>"", "environment_id"=>"5", "content_source_id"=>"2", "architecture_id"=>"1", "parent_id"=>""}}
It also seems like a UI only issue and have something to do with the Operating System selection or association with the host or hostgroup in question. If i don't select any OS for the Host or Hostgroup and try to reproduce the issue, It won't happen. The PXELoader value will not change.
The end-user has upgraded to Sat 6.14 and the issue is resolved for them. I am good with the BZ fix for now i.e. I don't need to have it on 6.13.z at this moment.