http://bugzilla.suse.com/show_bug.cgi?id=1078716 http://bugzilla.suse.com/show_bug.cgi?id=1078716#c1 Ancor Gonzalez Sosa changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |ancor@suse.com --- Comment #1 from Ancor Gonzalez Sosa --- The problem is that GuidedSetup.initial was unable to create a valid proposal (likely because /dev/vda is too small for Kubic requirements). But instead of reporting an "storage proposal not possible" error, it crashed when trying to assign the non-existing proposal here https://github.com/yast/yast-storage-ng/blob/master/src/lib/y2storage/client... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1078716 http://bugzilla.suse.com/show_bug.cgi?id=1078716#c3 --- Comment #3 from Ancor Gonzalez Sosa --- (In reply to Jason Evans from comment #2)

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

...

The problem is that GuidedSetup.initial was unable to create a valid proposal (likely because /dev/vda is too small for Kubic requirements). But instead of reporting an "storage proposal not possible" error, it crashed when trying to assign the non-existing proposal here

https://github.com/yast/yast-storage-ng/blob/master/src/lib/y2storage/ clients/partitions_proposal.rb#L163

Cool, thanks for the info. I increased the qcow to 40G and it's working now. Please close the bug.

I would not. The bug is still valid since it should have presented an understandable error and disabled the "Install" button. Instead, it showed a (kind of cryptic) error pop-up. I had to look into the logs to know what the problem was. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1078716 http://bugzilla.suse.com/show_bug.cgi?id=1078716#c5 Ancor Gonzalez Sosa changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Ancor Gonzalez Sosa --- I checked this and I'm 99.9% sure it was fixed a long time ago and the bug report was just overlooked and not closed. Feel free to reopen otherwise. -- You are receiving this mail because: You are on the CC list for the bug.