Bug ID | 1192287 |
---|---|
Summary | Creates extra snapshot 2 in MicroOS |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | YaST2 |
Assignee | yast2-maintainers@suse.de |
Reporter | aplanas@suse.com |
QA Contact | jsrain@suse.com |
Found By | --- |
Blocker | --- |
A fresh MicroOS installation via YaST (MicroOS role) shows an extra snapshot2 that is not the default one: # snapper ls -a # | Type | Pre # | Date | User | Used Space | Cleanup | Description | Userdata ---+--------+-------+--------------------------+------+------------+---------+-----------------------+-------------- 0 | single | | | root | | | current | 1* | single | | Wed Nov 3 09:36:13 2021 | root | 11.86 MiB | | first root filesystem | 2 | single | | Wed Nov 3 09:38:32 2021 | root | 10.16 MiB | number | after installation | important=yes After the first boot seems that the difference is only in the SElinux labels. The default one (1) currently have the labels, and not the second one (this is expected) # btrfs send --no-data -p /.snapshots/1/snapshot /.snapshots/2/snapshot | btrfs receive --dump | less (bunch of selinux and access time diffs) IMHO YaST / snapper should not create this second snapshot, as can cause confusion later during cleaning / rollback.