Bug 965213
Summary: | poor handling of user ignoring one disk of an existing md array via ignoredisk | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Robert Lightfoot <BobLfoot> | ||||||||||||||||||||||||||
Component: | python-blivet | Assignee: | David Lehman <dlehman> | ||||||||||||||||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||||||||
Version: | 19 | CC: | anaconda-maint-list, awilliam, bcl, dlehman, dshea, g.kaviyarasu, jonathan, mkolman, robatino, sbueno, vanmeeuwen+fedora | ||||||||||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||||||||
Hardware: | i686 | ||||||||||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||||||||||
Whiteboard: | abrt_hash:04bcc6eff86cdc2b71b0d3719683ca29d9f1407b7cdcd3860cfb440c185b14a9 AcceptedFreezeException RejectedBlocker | ||||||||||||||||||||||||||||
Fixed In Version: | pykickstart-1.99.32-1.fc19 | Doc Type: | Bug Fix | ||||||||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||||||||
Last Closed: | 2013-06-18 06:17:58 UTC | Type: | --- | ||||||||||||||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||||||
Embargoed: | |||||||||||||||||||||||||||||
Bug Depends On: | |||||||||||||||||||||||||||||
Bug Blocks: | 834091 | ||||||||||||||||||||||||||||
Attachments: |
|
Description
Robert Lightfoot
2013-05-20 17:54:27 UTC
Created attachment 750674 [details]
File: anaconda-tb
Created attachment 750675 [details]
File: anaconda.log
Created attachment 750676 [details]
File: backtrace
Created attachment 750677 [details]
File: environ
Created attachment 750678 [details]
File: ifcfg.log
Created attachment 750679 [details]
File: ks.cfg
Created attachment 750680 [details]
File: lsblk_output
Created attachment 750681 [details]
File: nmcli_dev_list
Created attachment 750682 [details]
File: packaging.log
Created attachment 750683 [details]
File: program.log
Created attachment 750684 [details]
File: storage.log
Created attachment 750685 [details]
File: syslog
There are two things going on that are probably wrong: 1. We hide ignored disks and devices that require them before deactivating all devices we found in the system to begin with. This means we won't deactivate devices that use any ignored disks. 2. We shouldn't be hiding devices that build on both ignored disks and non-ignored disks. Instead, those devices should appear as incomplete or degraded, since that will be the case if the user wipes one of the disks. I can also add that this was done with a working kickstart and was going from a working software raid system {sda;sdb} to a single disk setup {sda}. Don't know if coming from software raid is important but that seems to be when this crops up. As going from a different single disk setup I did not hit the bug again. Discussed at 2013-05-29 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-05-29/f19final-blocker-review-1.2013-05-29-16.02.log.txt . Note: kickstart issues are still being evaluated on a case-by-case basis as we still didn't get around to writing criteria beyond the very basic one we have in Beta. In the end we decided to reject this as a blocker, with the input of dlehman: he considers that we don't undertake to work with absolutely every messy configuration people manage to throw at us via kickstart. This is triggered by 'ignoring' parts of a multi-disk device (mdraid set, LVM VG, btrfs volume...) via the kickstart ignoredisk command, so the workaround is not to do that, or to clean up your multi-disk devices before throwing them at anaconda. However, it's accepted as a freeze exception issue: we think it would be good to get a fix for this into F19 final if possible. pykickstart-1.99.32-1.fc19,python-blivet-0.16-1.fc19,anaconda-19.30.6-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/pykickstart-1.99.32-1.fc19,python-blivet-0.16-1.fc19,anaconda-19.30.6-1.fc19 Package anaconda-19.30.7-1.fc19, pykickstart-1.99.32-1.fc19, python-blivet-0.16-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-19.30.7-1.fc19 pykickstart-1.99.32-1.fc19 python-blivet-0.16-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-10913/pykickstart-1.99.32-1.fc19,python-blivet-0.16-1.fc19,anaconda-19.30.7-1.fc19 then log in and leave karma (feedback). pykickstart-1.99.32-1.fc19, python-blivet-0.16-1.fc19, anaconda-19.30.8-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |