http://bugzilla.opensuse.org/show_bug.cgi?id=966637 Bug ID: 966637 Summary: Snapper configuration not automatically set when importing mount points from disk Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: gtettamanzi@gmail.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0 Build Identifier: Info: Tumbleweed net installer 20160209-0 - snapper 0.2.10-1.1 I have a /boot partition + a LVM partition; inside the LVM partition I have a logical btrfs / partition and a logical XFS /home one. I was running Tumbleweed with snapper activated and running. I decided to fresh install my system importing the mount points from the existing ones (expert partitioner -> rescan device first and import mount points second -> accept). After booting in the fresh installed system, I ran snapper list-configs: no configuration was available. I expected the installer to set up the "root" config by default. Work around: manual set up of "root" configuration by running a "sudo snapper create-config /" command and editing the /etc/snapper/configs/root file for tweaking configuration (As a desktop user, I want no timeline snapshots, only number snapshots and a reduced number of them). Reproducible: Always Steps to Reproduce: 1.launch the installer 2. at the partition set up step choose "Expert partitioner" 3. click on "Rescan device" 4. click on "Import mount points" and accept, going ahead with the full installation process 5. check after the first boot if there's in place a snapper configuration (run snapper list-configs) Actual Results: No "root" config automatically set. Expected Results: "root" configuration automatically set up. I had the same behavior in a previous re installation process - I guess it's not a regression of the installation media I used this time. -- You are receiving this mail because: You are on the CC list for the bug.