https://bugzilla.suse.com/show_bug.cgi?id=1205374 https://bugzilla.suse.com/show_bug.cgi?id=1205374#c15 Ancor Gonzalez Sosa <ancor@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor@suse.com --- Comment #15 from Ancor Gonzalez Sosa <ancor@suse.com> --- (In reply to Felix Miata from comment #13)

Why doesn't the partitioner start anew when it has been canceled out of and later returned to?

Because that would imply we need re-analyze the whole system on every Partitioner run. That may consist on dozens of local and remote disks, LVM structures, encryption layers that are demanding to be decrypting and whatnot. And the storage structure that gets read affects other aspects and not only the Partitioner, so it's not something that can be reset lightheartedly. If you need to re-read the storage devices because you did some changes behind YaST's back, you can do it on-demand with the already mentioned "Rescan Devices" option. That's what the option is there for. -- You are receiving this mail because: You are on the CC list for the bug.