Bugzilla – Bug 941871
Snapper not configured on a minimal install
Last modified: 2015-08-26 10:09:27 UTC
Created attachment 643956 [details] y2logs As the subject sets, a minimal install of Leap 42.1 does not configure snapper as part of the installation (it's possible default installs also dont, but I've only tested it manually with minimal here) Steps to reproduce Install Leap 42.1 Milestone 1 or newer builds Select Minimal Installation (Server) on the Desktop Selection, all default options Boot the resulting system Expected Results snapper list-configs should list / Actual Results snapper list-configs has no configs Loading up YaST software selection fails, producing the following message when they start > The config 'root' does not exist. Likely snapper is not configured. The command then times out, never letting the user get to YaST - this is why I've marked the bug as Critical, as the YaST Software Selection module is kind of super important y2logs are attached
Huha - can you check it?
From the logs: 2015-08-16 00:31:05 <1> mirax.geekodu.de(3242) [Ruby] modules/StorageSnapper.rb:76 configuring snapper for root fs - step 1 2015-08-16 00:31:05 <3> mirax.geekodu.de(3242) [bash] ShellCommand.cc(shellcommand):78 sh: /usr/lib/snapper/installation-helper: No such file or directory 2015-08-16 00:31:05 <1> mirax.geekodu.de(3242) [Ruby] modules/StorageSnapper.rb:48 exit: 127 2015-08-16 00:31:05 <1> mirax.geekodu.de(3242) [Ruby] modules/StorageSnapper.rb:50 stderr sh: /usr/lib/snapper/installation-helper: No such file or directory 2015-08-16 00:31:05 <3> mirax.geekodu.de(3242) [Ruby] modules/StorageSnapper.rb:83 configuring snapper for root fs failed /usr/lib/snapper/installation-helper is part of the "snapper" package, and it should also be in the inst-sys. IIRC "installation-helper step 1" is called from within the inst-sys. I don't see how this could be missing there.
For the record: I just talked to Richard, and it seems to be possible that snapper is on that distro, but not in the inst-sys yet. Need to check.
Same as bug #943066. *** This bug has been marked as a duplicate of bug 943066 ***