Open atanasdinov opened 1 month ago
This is currently happening due to the limitation in the transactional-update run zypper migration
command. It does not seem to propagate the exit codes of the commands that are executed within the run
block, hence always resulting in a 0
exit code.
This will be fixed once transactional-update migration
supports the flags that zypper migration
does. Then we will not be limited by the aforementioned problem and the 1
exit code will be properly propagated and handled. Which will result in a failure of the pod instead of it being marked as "Completed".
A non-registered node is incapable of finding the upgrade path to the next SL Micro version e.g. trying to upgrade from 5.5 to 6.0 looks like this:
After this the node is restarted and SUC considers the plan as finished. However, since we check against the pretty name of the operating system, as a done criteria for our condition, the reconciliation on our upgrade plan hangs indefinitely and cannot proceed.