action #88786

Updated by riafarov 7 months ago

We have many differences in the schedules only because of the way reboot is handled after installation.
As we already did for the bootloader, it allowed us not to have separate schedules due to those differences.

We want to explore possibilities and agree on the approach, so we want to explore possibilities before implementing it.

The scenario we can use as an example is `minimal+base_yast` minimal+base_yast in our ob group which is executed on all backends (except ipmi).

Options: # Acceptance criteria
* 1. There is an atomic module to handle reboot which can be scheduled for all backends
* Some way to unify it on scheduling level not to duplicate it