http://bugzilla.suse.com/show_bug.cgi?id=1094877 http://bugzilla.suse.com/show_bug.cgi?id=1094877#c4 José Iván López González changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID Flags|needinfo?(jlopez@suse.com) | --- Comment #4 from José Iván López González --- (In reply to Stefan Hundhammer from comment #3)

I just found out that this check is no longer that easy: We now check if the disk contains the installation repositories. That was a fairly recent change.

https://github.com/yast/yast-storage-ng/blob/master/src/lib/y2storage/ disk_analyzer.rb#L295

Commit:

https://github.com/yast/yast-storage-ng/blob/master/src/lib/y2storage/ disk_analyzer.rb#L295

Pull request:

https://github.com/yast/yast-storage-ng/pull/643

This explains the changed behaviour. I am just not sure if the behaviour you just observed is the desired one. It is a change, that much is sure; I believe it is a change for the better, but I'd rather make sure of that.

Ivan?

Effectively, there was a bug in the detection of installation medium that was already fixed. Previous that fix, the proposal could wrongly use the installation medium disk during the installation process. The installation medium should not be used to install over it because that disk might contain the needed repositories for the packages to install during the installation. Now, that error is fixed and the installation medium is not "visible" for the proposal anymore. If the user wants to use it for the installation, he has to do it with the Expert Partitioner (under his own responsibility). In this test, the parameter install=hd:/install.iso was used, so /dev/vdb is the installation medium, and as consequence, it is not used by the proposal. See this bug for more info: https://bugzilla.suse.com/show_bug.cgi?id=1091047 -- You are receiving this mail because: You are on the CC list for the bug.