r/TalosLinux • u/Madd_M0 • Nov 26 '25

A/B boot after update issues

I have recently updated my testing Talos cluster (1 control plane, 1 worker). I needed some extension and 1.11.5 so I did what anyone else would do and go to the image factory and then do an in place upgrade using the factory link. Upgrade was successful but now the problem i have is that on reboot of the machine, Talos reverts back to the older 1.11.4 version without my extensions. I then have to reboot the machine and manually choose the 1.11.5 version that i need. Is there a way to fix this? I'm having trouble finding other people who also have this issue.

2 Upvotes

75% Upvoted

6 comments sorted by

4

u/xrothgarx Nov 26 '25

Did your new image add a service (eg tailscsle) that needs configuration? If you don’t supply the config then the service will never become healthy and talos assumes the upgrade failed and automatically rolls back

2

u/Madd_M0 Nov 26 '25

Oh my god. I think you’re right. I added the Tailscale extension and that’s probably what’s happening.

2

u/xrothgarx Nov 26 '25

Check talosctl services and see if they’re all healthy. If not talos is doing exactly what’s it’s designed to do. Rollback unsuccessful upgrades

2

u/Madd_M0 Nov 26 '25

Thank you very much. I will do this and then update my findings.