http://bugzilla.suse.com/show_bug.cgi?id=1146933 http://bugzilla.suse.com/show_bug.cgi?id=1146933#c2 William Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(william.brown@sus | |e.com) | --- Comment #2 from William Brown --- I'm sorry I can't - I already have reinstalled the machines and lost the logs as I did manual partition clean ups. It would be pretty easy to recreate this situation in a virtual machine I would think though? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1146933 http://bugzilla.suse.com/show_bug.cgi?id=1146933#c3 David Diaz changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(william.brown@sus | |e.com) --- Comment #3 from David Diaz --- (In reply to William Brown from comment #2)

I'm sorry I can't - I already have reinstalled the machines and lost the logs as I did manual partition clean ups. It would be pretty easy to recreate this situation in a virtual machine I would think though?

Ok, no problem. Just a couple of questions more. When you said, (In reply to William Brown from comment #0)

[...] yast will error as it does not recognise the device [...]

Do you mean that the installer displayed a message like following?

Detected LVM logical volumes of unsupported types: <WHATEVER>

These logical volumes are ignored. Operations on the

corresponding volume groups may fail.

If so, are you requesting to do something more than just warning about that situation? Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1146933 http://bugzilla.suse.com/show_bug.cgi?id=1146933#c5 David Diaz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #5 from David Diaz --- (In reply to William Brown from comment #4)

Yes, that seems like the error message that I saw - though I don't remember it being so harsh in wording. Maybe from a UX perspective because of the green (good) + small text it was easy to just overlook this as a "gentle warning" rather than a strong warning like it's intended.

Perhaps the "accept" could be coloured red, and the text changed to "Volume group operations may FAIL: <reason>" to help move the impact to the first part of the sentence so that it's harder to overlook.

It could also be good to have a remediation step so the text reads like:

Volume Group operations may FAIL. Some Logical Volumes may be IGNORED.

Detected LVM logical volumes of unsupported types: <WHATEVER>

To resolve this you should inspect Volume Group <VG> and restart the installation.

[ <GREEN>: Go To SHELL to fix ] [ <RED>: Accept the consequences ]

Is that a reasonable suggestion?

Saying this, it would be pretty good if yast did know what an lvmcache pool device was too :)

Thank you for the feedback. I cannot promise anything regarding to the final decision, but I am going to put this report under the PO radar. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1146933 Ancor Gonzalez Sosa changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://trello.com/c/cJUUXt | |3J/152-allow-to-wipe-device | |-if-probe-failed CC| |ancor@suse.com -- You are receiving this mail because: You are on the CC list for the bug.