Bug 888089
Summary: | ValueError: A RAID0 set requires at least 2 members | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Chris Murphy <bugzilla> | ||||||||||||||||||
Component: | anaconda | Assignee: | David Lehman <dlehman> | ||||||||||||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||
Version: | 18 | CC: | anaconda-maint-list, awilliam, bcl, g.kaviyarasu, jonathan, jreznik, robatino, sbueno, vanmeeuwen+fedora | ||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||
Whiteboard: | abrt_hash:dc1e8e7bf48151b5568b3652cd573da2244b943d55f81c120abb0e2fb38c7156 AcceptedBlocker | ||||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||
Last Closed: | 2013-01-08 21:33:31 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: | 752661 | ||||||||||||||||||||
Attachments: |
|
Description
Chris Murphy
2012-12-18 00:33:18 UTC
Created attachment 665206 [details]
File: anaconda-tb
Created attachment 665207 [details]
File: anaconda.log
Created attachment 665208 [details]
File: environ
Created attachment 665209 [details]
File: ifcfg.log
Created attachment 665210 [details]
File: messages
Created attachment 665211 [details]
File: program.log
Created attachment 665212 [details]
File: storage.log
Steps to reproduce: 1. Two new virtual disks. 2. Launch installer > Installation Destination > Choose both disks. 3. Choose "customize the partitioning" checkbox to go to Manual Partitioning. 4. Manual Partitioning, click "click here to create them automatically" 5. Boot is already selected, click on Customize > Device Type set to RAID. 6. Click on Root Results: Crash Expected: a.) Don't let me do invalid things; or b.) don't crash. Regression: If I do it this way, it works (doesn't crash, installs, and boots.) 1. click on swap, set to standard partitioning, apply changes. 2. click on root, set to RAID0, apply changes. 3. click on boot, set to RAID0, apply changes. Additional info: Proposing as blocker: F18 Beta Release Criterion #11: must be able to install to RAID-0 *except* for /boot. i.e. it is obviously an invalid operation. F18 Beta Release Criterion #10: Installer should... Reject obviously invalid operations without crashing. The device is switched to md, but one of the two disks has no free space so it fails. We need to catch this exception so it can be handled cleanly. Sounds like another bug because both disks have only free space, not partitioned, and are identical in size. Discussed at 2012-12-19 blocker review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-12-19/f18final-blocker-review-6.2012-12-19-17.02.log.txt . Accepted as a blocker per criterion "The installer's custom partitioning mode must be capable of the following ... Rejecting obviously invalid operations without crashing". So, the patch looks to have been acked: https://lists.fedorahosted.org/pipermail/anaconda-patches/2012-December/002581.html but never pushed to f18-branch: http://git.fedorahosted.org/cgit/anaconda.git/log/?h=f18-branch I don't see it there. David, Brian, why the hold-up in pushing this? Can it please get pushed? Thanks. That patch referred to the wrong bz#. It was pushed with the right one, bug 885378 (In reply to comment #13) > That patch referred to the wrong bz#. It was pushed with the right one, bug > 885378 Well, this looks like a correct one - https://lists.fedorahosted.org/pipermail/anaconda-patches/2012-December/002578.html and got acked (ValueError to DeviceError to catch the exception as mentioned above in comment #9), the one you refer to is [PATCH 2/3]. Created attachment 671770 [details]
anaconda-tb-qjilrm
Still get a crash with 18.38.8-1, libreport says it's a dup of this bug. Attaching a current anaconda-tb.
So per IRC discussion yesterday, this just needed the correct patch to be cherry picked from master to f18-branch. Has someone done that yet? Yes. It was cherry-picked and pushed earlier today. anaconda-18.37.9-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.37.9-1.fc18 anaconda-18.37.9-1.fc18 fixes this bug. Package anaconda-18.37.9-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.37.9-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-0206/anaconda-18.37.9-1.fc18 then log in and leave karma (feedback). anaconda-18.37.10-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.37.10-1.fc18 anaconda-18.37.11-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.37.11-1.fc18 Still fixed in anaconda-18.37.11-1.fc18. anaconda-18.37.11-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |