|
Bugzilla – Full Text Bug Listing |
| Summary: | LVM cache pool devices cause yast to be unable to clear partitions | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | William Brown <william.brown> |
| Component: | YaST2 | Assignee: | YaST Team <yast-internal> |
| Status: | CONFIRMED --- | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | ancor, aschnell, dgonzalez, william.brown |
| Version: | Leap 15.1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| URL: | https://trello.com/c/cJUUXt3J/152-allow-to-wipe-device-if-probe-failed | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
William Brown
2019-08-23 00:20:49 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 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? (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! 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 :) (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. |