http://bugzilla.suse.com/show_bug.cgi?id=1127766 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1127766 Olaf Hering changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ohering@suse.com) | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1127766 http://bugzilla.suse.com/show_bug.cgi?id=1127766#c5 Ancor Gonzalez Sosa changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(ohering@suse.com) --- Comment #5 from Ancor Gonzalez Sosa --- (In reply to Ancor Gonzalez Sosa from comment #4)

(In reply to Stefan Hundhammer from comment #1)

...

This "installation-helper" call tries to create a pre-update snapshot. It shouldn't do that in the first place. That this fails because there is no .snapshots directory is only a consequence of that.

Now I wonder why it even wants to create that snapshot.

From the attached logs:

Checking if Snapper is configured: "/usr/bin/snapper --no-dbus --root=%{root} list-configs | /usr/bin/grep "^root " >/dev/null" returned: {"exit"=>0, "stderr"=>"", "stdout"=>""}

Since the exit code of that command is zero, the installer concludes Snapper if configured and a snapshot can/must be performed.

Needless to say, %{root} is substituted by /mnt when the command is executed. Olaf, since your system is so special, would you mind to paste the full output of this command? /usr/bin/snapper --no-dbus --root=/mnt list-configs Executed in the installation media, after the system to upgrade has been mounted. ==== If that's too hard, I guess it would be enough to just execute this in any of the systems that are installed into that filesystem: /usr/bin/snapper --no-dbus list-configs ==== Or alternatively do something like this with a rescue system ...activate the volume... mount -t btrfs /dev/sd240_crypt_lvm/sd240_btrfs /mnt /usr/bin/snapper --no-dbus --root=/mnt list-configs The first alternative would be the best, but whatever works for you... I guess you get the idea. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1127766 http://bugzilla.suse.com/show_bug.cgi?id=1127766#c7 --- Comment #7 from Olaf Hering --- 0:esprimo:~ # cat /mnt/etc/snapper/configs/root # subvolume to snapshot SUBVOLUME="/" # filesystem type FSTYPE="btrfs" # users and groups allowed to work with config ALLOW_USERS="" ALLOW_GROUPS="" # start comparing pre- and post-snapshot in background after creating # post-snapshot BACKGROUND_COMPARISON="yes" # run daily number cleanup NUMBER_CLEANUP="yes" # limit for number cleanup NUMBER_MIN_AGE="1800" NUMBER_LIMIT="50" # create hourly snapshots TIMELINE_CREATE="yes" # cleanup hourly snapshots after some time TIMELINE_CLEANUP="yes" # limits for timeline cleanup TIMELINE_MIN_AGE="1800" TIMELINE_LIMIT_HOURLY="10" TIMELINE_LIMIT_DAILY="10" TIMELINE_LIMIT_MONTHLY="10" TIMELINE_LIMIT_YEARLY="10" # cleanup empty pre-post-pairs EMPTY_PRE_POST_CLEANUP="yes" # limits for empty pre-post-pair cleanup EMPTY_PRE_POST_MIN_AGE="1800" 0:esprimo:~ # ls -l /mnt/etc/snapper/configs/root -rw-r--r-- 1 root root 800 Mar 22 2016 /mnt/etc/snapper/configs/root I'm sure I never used snapper, perhaps a config as included in earlier pkgs? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1127766 http://bugzilla.suse.com/show_bug.cgi?id=1127766#c9 Ancor Gonzalez Sosa changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(aschnell@suse.com | |) --- Comment #9 from Ancor Gonzalez Sosa --- (In reply to Arvin Schnell from comment #8)

(In reply to Ancor Gonzalez Sosa from comment #4)

...

Since the exit code of that command is zero, the installer concludes Snapper is configured and a snapshot can/must be performed.

Which normally is fine. But the 'list-configs' command does not verify that the configs are actually sound/available. Here that is not the case.

And how can YaST check that? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1127766 Ancor Gonzalez Sosa changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED URL| |https://trello.com/c/pMzijc | |Rv Assignee|yast2-maintainers@suse.de |yast-internal@suse.de -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1127766 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugzilla.suse.com/sh | |ow_bug.cgi?id=1160918 -- You are receiving this mail because: You are on the CC list for the bug.