debian/ubuntu-pro-client.postinst defines mark_reboot_cmds_as_needed as well as REBOOT_CMD_MARKER_FILE. These might be tech debt from the package rename from commit 4ad6b5e and could be removed, unless there’s a good reason for these to remain?
Expected behavior
Make use of the marker file more clear if needed or replace with a better way to handle fips package updates on reboot
Current behavior
The marker file is currently only created in the debian/ubuntu-advantage-tools.postinst. Should the marker file instead be moved to check for FIPS only handling? Currently in reboot_cmds.py the use of the marker file is used for fips package updates.
Description of the bug
debian/ubuntu-pro-client.postinst
definesmark_reboot_cmds_as_needed
as well asREBOOT_CMD_MARKER_FILE
. These might be tech debt from the package rename from commit 4ad6b5e and could be removed, unless there’s a good reason for these to remain?Expected behavior
Make use of the marker file more clear if needed or replace with a better way to handle fips package updates on reboot
Current behavior
The marker file is currently only created in the
debian/ubuntu-advantage-tools.postinst
. Should the marker file instead be moved to check for FIPS only handling? Currently inreboot_cmds.py
the use of the marker file is used for fips package updates.To Reproduce
n/a
System information:
n/a
Additional context
n/a