Bugzilla – Bug 1212203
fails to boot to the new system after manual transational update
Last modified: 2023-06-12 09:45:58 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36 Build Identifier: i tried many times but it doesnt work , i disabled the automatic transactional update timer and tried to manually update several times but it only works if ignore-unknown is added to the command. (which i found from an old related bug , but cannot find now as it was closed.) so, i can do "sudo transactional-update run zypper --ignore-unknown dup" and it magically works but if i use the normal "sudo transactional-update dup" and "sudo reboot" it just boots to the snapshot before update. Reproducible: Always Steps to Reproduce: 1.try manually updating with "sudo transactional-update dup" 2.there will not be any errors except "zypper --no-cd dup on /.snapshots/5/snapshot failed with exit code 106! Use '--interactive' for manual problem resolution." after the update 3.sudo reboot Actual Results: you will boot in the original snapshot without the update. Expected Results: you should boot in the updated system right now on kernel 6.3.6 snapshot 20230608 my system is i5 6300u (dell e5470 laptop)
(In reply to Vishal Goswami from comment #0) > 2.there will not be any errors except "zypper --no-cd dup on > /.snapshots/5/snapshot failed with exit code 106! > Use '--interactive' for manual problem resolution." after the update from zypper manual page: " 106 - ZYPPER_EXIT_INF_REPOS_SKIPPED Some repository had to be disabled temporarily because it failed to refresh. You should check your repository configuration (e.g. zypper ref -f)." Please fix your repositories. It's not the fault of transactional-update or zypper, if your repository setup creates errors. > 3.sudo reboot > Actual Results: > you will boot in the original snapshot without the update. Ok, so everything is working: transactional-update could not apply the updates without errors and thus does not boot into a possible broken system. > Expected Results: > you should boot in the updated system NO! transactional-update should never ever boot into a possible broken system! If you want that, you don't need transactional-update but you can stay with a traditional system.
As Thorsten already pointed out this is intentional behavior: Ignoring unavailable repositories may even lead to system downgrades, so this is treated as an error. Please remove, disable or fix the repository in question.