![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1192287
https://bugzilla.suse.com/show_bug.cgi?id=1192287#c6
--- Comment #6 from Alberto Planas Dominguez
It's this PR: https://github.com/yast/yast-installation/pull/287
This is definitely wanted functionality - snapshot after all is installed and configured. It's there for ages.
Alberto, why exactly you would like to remove such snapshot now?
In MicroOS / SLE Micro order the snapshots is in a different way. This PR is for the snapper model that we have in TW / SLE, where the current snapshot is changed during the upgrade, was we make a pre and post snapshot to have a place to do the rollback. In MicroOS we live in the last snapshot, that is the default one and a `t-u dup` will create a new snapshot based on the active one, that will become the new active for the next reboot. This snapshot#2 in MicroOS / SLE Micro should not be present IMHO, as is a remanent of the old model. You can see that yourself: install a new MicroOS from scratch and the first boot will be over the snaphot#1 (default and active). Snapshot#2 is present and unlabeled (so broken). Do a "t-u pkg in" and this will create snapshot#3 based on snapshot#1, and if all goes OK #3 is the new default one that will be active after the reboot. In this operation #2 was never used, never default and never active. But is still unlabeled and can be a candidate for a rollback (t-u rollback), that can be problematic. -- You are receiving this mail because: You are on the CC list for the bug.