📖 ~1 min read
Table of contents
Symptom & Impact
`transactional-update` ends success, but `snapper status` shows no new default after reboot.
Environment & Reproduction
Happens on systems where the boot loader entry was not refreshed by the tukit hook.
Root Cause Analysis
`tukit reboot` was skipped or interrupted, leaving the new snapshot non-default.
Quick Triage
Verify the pending snapshot: `snapper –no-headers list | grep ‘+’`.
Step-by-Step Diagnosis
Run `transactional-update –dry-run` to confirm pending state, then check `/etc/grub.d/`.

Solution – Primary Fix
Re-execute `transactional-update apply` followed by `systemctl reboot`.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Use `tukit close` and a manual snapshot-set-default cycle if tukit hangs.
Verification & Acceptance Criteria
After reboot `snapper status` lists the new snapshot as default and read-write.
Rollback Plan
Roll back via `transactional-update rollback last` if the new snapshot breaks services.
Prevention & Hardening
Wrap transactional-update runs in a CI smoke-test before fleet rollout.
Related Errors & Cross-Refs
Pairs with `grub2-mkconfig` warnings when boot env is stale.
Related tutorial: View the step-by-step tutorial for sles-16.
View all sles-16 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
transactional-update and tukit manuals.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.