Hmm well that looks like it successfully upgrades but then fails the boot environmen check at the first boot after that. Hence it reverts to the old 24.11 BE.
It should show an alert in 24.11 confirming that it reverted to a previous BE.
If you check the list of BEs you should see some created for the upgrades that are marked as failed.
It's odd it doesn't show that in the console output though. It could be simply timing out at the first boot if something there is taking a very long time? How large is the config? Or does it have anything unusual that is ripping up the config update script perhaps?