Bug 48122 - Regenerate pxelinux config files when kernel/initrd are changed
Regenerate pxelinux config files when kernel/initrd are changed
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UCS Net Installer
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-11-08 16:56 CET by Valentin Heidelberger
Modified: 2021-05-14 16:34 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Valentin Heidelberger univentionstaff 2018-11-08 16:56:57 CET
PXE Linux configs are saved for individual computers in the directory /var/lib/univention-client-boot/pxelinux.cfg/

Via the UCRVs pxe/installer/kernel and pxe/installer/initrd a certain release installer can be specified. The values of these variables are used when the pxelinux configs are generated in /var/lib/univention-client-boot/pxelinux.cfg/

The pxelinux config file for a certain computer object is only regenerated when reinstallation attributes of that attribute are changed (e.g. reinstallation deactivated and activated again). 

I propose to trigger a rewrite of all existing pxelinux cfgs when 
pxe/installer/(kernel|initrd) is changed.

If a user decides to change the kernel and initrd to use for pxe installations, they'd have to change reinstallation attributes for every single computer to actually apply the new config.
Comment 1 Ingo Steuwer univentionstaff 2021-05-14 15:42:24 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.