Bug 1146933 - LVM cache pool devices cause yast to be unable to clear partitions
LVM cache pool devices cause yast to be unable to clear partitions
Status: CONFIRMED
Classification: openSUSE
Product: openSUSE Distribution
Classification: openSUSE
Component: YaST2
Leap 15.1
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: YaST Team
Jiri Srain
https://trello.com/c/cJUUXt3J/152-all...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-08-23 00:20 UTC by William Brown
Modified: 2019-12-19 16:30 UTC (History)
4 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description William Brown 2019-08-23 00:20:49 UTC
During a system reinstall, if an lvm cachepool device exists on the system lv, yast will error as it does not recognise the device. Subsequent it then fails to partition and the reinstall will fail.

To reproduce, you can configure a system post install to have a cachepool on system, then attempt a reinstall. (This was found due to https://bugzilla.suse.com/show_bug.cgi?id=1146932)
Comment 1 David Diaz 2019-08-23 08:32:12 UTC
Hi William.

Would it be possible to collect the YaST logs[1] during the reinstall and attach them here? They will be helpful.

Thanks!

[1] https://en.opensuse.org/openSUSE:Report_a_YaST_bug
Comment 2 William Brown 2019-08-26 02:51:25 UTC
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?
Comment 3 David Diaz 2019-08-26 15:12:56 UTC
(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!
Comment 4 William Brown 2019-08-26 22:27:29 UTC
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 :)
Comment 5 David Diaz 2019-08-27 07:12:59 UTC
(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.