Bug 1022203 - Unable to change non-RAID partition size in mixed RAID, non RAID setup
Summary: Unable to change non-RAID partition size in mixed RAID, non RAID setup
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F20FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2013-10-22 17:09 UTC by David Lehman
Modified: 2013-11-05 03:39 UTC (History)
2 users (show)

Fixed In Version: anaconda-20.25.4-1.fc20
Clone Of: 1020370
Environment:
Last Closed: 2013-11-05 03:39:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description David Lehman 2013-10-22 17:09:29 UTC
+++ This bug was initially created as a clone of Bug #1020370 +++

Description of problem:
I have a system with two disk drives of different size. By creating RAID1 partition over the whole smaller disk and part of the larger one, there is still some free space remaining on the larger one. If I create partition on the remaining of the larger disk I'm unable to change its size. Anaconda reports:

The RAID level you have selected(raid1) requires more disks(2) than you currently have selected(1).

Version-Release number of selected component (if applicable):
anaconda-20.25.1-1

How reproducible:
always

Steps to Reproduce:
1. Prepare VM with two disks, let's say 20GB and 8GB
2. Start installation, select manual partitioning
3. Create / partition, do not specify size
4. Change / partition Device type to RAID, leave RAID level as RAID1
5. Click Update settings, anaconda reports 12.28GB of available space
6. Add swap partition, do not specify size
7. Try to reduce swap partition size by 1GB and click update

Actual results:
Anaconda complains with insufficient number of raid devices message.

Expected results:
Anaconda should allow to change non-RAID partition size

Additional info:

Comment 1 David Lehman 2013-10-22 17:11:41 UTC
I have just tested a patch for this issue.

Comment 2 Fedora Update System 2013-10-26 01:10:44 UTC
anaconda-20.25.4-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/anaconda-20.25.4-1.fc20

Comment 3 Fedora Update System 2013-10-26 18:49:22 UTC
Package anaconda-20.25.4-1.fc20, pykickstart-1.99.44-1.fc20, python-blivet-0.23.2-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-20.25.4-1.fc20 pykickstart-1.99.44-1.fc20 python-blivet-0.23.2-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-20033/pykickstart-1.99.44-1.fc20,python-blivet-0.23.2-1.fc20,anaconda-20.25.4-1.fc20
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2013-11-05 03:39:06 UTC
anaconda-20.25.4-1.fc20, pykickstart-1.99.44-1.fc20, python-blivet-0.23.2-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.