Bug 71012
Summary: | Changing partition from ext3 -> SW Raid confuses disk druid | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Glen A. Foster <glen.foster> |
Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | tao |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | ia64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-07-14 22:40:26 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: |
Description
Glen A. Foster
2002-08-07 19:53:53 UTC
I can't reproduce this here -- are you sure that you didn't accidentally unselect one of the partitions? I just reproduced the issue with Derry-0821. Here's how I did it: [Harfware == Wilson Peak with 2 drives] Step #1: install a distribution.(min. install is OK) formatted as follows: - clear out all partitions on /dev/hda AND /dev/hdb - create /boot/efi, swap, etc. == CREATE / as EXACTLY 15000M, ext3 file system - continue with install (should work fine) -- in fact I was wondering if a reboot following the first package installation would shorten the time required to reproduce this, since the partitions are formatted. Step #2: re-install (any type) - keep /boot/efi and swap - create 15000M "Software RAID" partition on /dev/hdb - select ext3 15000M partition on /dev/hda, press EDIT == select "Filesystem Options" --> tell it to format the partition as "Software RAID" --> press OK - press "RAID" button ... there's your error message. Says you must have 2 RAID partitions (and disk druid tells me I do) so something is amiss -- either the counting of SW RAID partitions, or the fact that I can re-format it as SW RAID. Dunno. If first install is minimal, whole procedure can take 20-30 minutes. QED. :-) Today's status meeting update: Jeremy says that there's an easy workaround to just delete the partition first. I think I need clarification here. Is the workaround to simply delete the partition something that *I* as the user should do, or is it something that anaconda needs to add to the code when the partition type is changed? As coded, anaconda puts the user into a position where a seemingly valid operation (I assume it's valid since the U/I lets me change this) cannot work. User interfaces with stringent usability design (ideally) should not allow a user to get into a function that cannot happen. So will this be repaired, or closed as NOTABUG? /me hopes the former. normalizing Version in Red Hat Linux Beta product ISSUE TRACKER 21402 opened as sev 2 I talked with Jeremy. This is fixed in Taroon and will not be fixed in AS2.1. The workaround for 2.1 is to have the user delete the partition first. Suggest you verify fixed in Taroon and we close the Bug. (also fixing release to RHEL since this appeared on Derry) It sounds like the decision is made. What particular information is being waited for -- HP's approval for this decision? If so, consider it given. If not, let me know what other information is needed, and reset this defect to NEEDINFO . Need confirmation that fixed in Taroon before closing Bug. What is the status of this bug? I have confirmed that the issue IS NOT FIXED with AS2.1 update 2. I have further confirmed that the issue IS FIXED in Taroon alpha 4, at least as far as determining that disk druid no longer complains and needing more RAID devices. Okay, fixed in Taroon, not going to be backported |