There are numerous people reporting they are stuck in a reboot loop when attempting upgrade. That's the worst outcome we can get, because suddenly their system is "bricked", and it's not easy to fix. Some of them might be Chinese, due to the this bug, but it seems not all of them. So there are some other issues as well.
We need to make failures more resistant. Because currently, when this fails to start, due to whatever dnf or python error, the system is stuck in a reboot loop, because /system-update is never removed:
We need to verify whether the $RELEASEVER envvar will work as intended. We can also create a bash script for this, if we don't want to have it all on a single command line. But I think this is really important, because we need to ensure people won't end up in reboot loops if the system-upgrade command fails to start for any reason.
There are numerous people reporting they are stuck in a reboot loop when attempting upgrade. That's the worst outcome we can get, because suddenly their system is "bricked", and it's not easy to fix. Some of them might be Chinese, due to the this bug, but it seems not all of them. So there are some other issues as well.
We need to make failures more resistant. Because currently, when this fails to start, due to whatever dnf or python error, the system is stuck in a reboot loop, because
/system-updateis never removed:I suggest to change it to something like this:
We need to verify whether the
$RELEASEVERenvvar will work as intended. We can also create a bash script for this, if we don't want to have it all on a single command line. But I think this is really important, because we need to ensure people won't end up in reboot loops if the system-upgrade command fails to start for any reason.