Bug 366341
Summary: | anaconda/kickstart - prompts on detecting read-only volumes even with ignoredisk | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Dean Samuels <dsamuels> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.0 | CC: | clusterman, ddumas, jrfuller, rick.beldin, rproffit, va6ualei |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-07-01 20:44: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: |
Description
Dean Samuels
2007-11-05 03:17:47 UTC
The problem here is that we still scan the drives to attempt to determine which filesystem labels are in use and which bootloader config options to present to the user. Even though we're not really going to write anything to them, we still need to read data from the ignored disks. ignoredisk really only refers to that certain disks should not be used when creating partitions and clearing devices. But do you have to post a "Read Only Disk" error for each one you come across that's read only? What if you have a SAN with hundreds of "read-only" LUNs? How can you automate that if you have to be on the console to click "OK" one hundred times? Maybe ignoredisk isn't the right parameter to deal with this, but *something* needs to. Johnray I notice this is a RHEL5 bug, but not one with a corresponding IT score. Is there a chance we can pursue this as a Fedora bug and once it's fixed up, close as NEXTRELEASE due to it being in RHEL6? I ask because I committed a patch today that should make ignoredisk work the way it should, and the way this bug report wants. However, it could use some testing. If you could test against rawhide (not F11 beta - patch is not there) and provide feedback, it would be very helpful in making sure we no longer have this problem going into RHEL6. Thanks. Is there any work around other than waiting until the next release of RHEL? We need a fix for this now. We have over 50 servers to upgrade to RHEL5. This bug stops us from doing our kickstarts. Ultimately, we need an option to ignore SAN that works on HP, IBM, Dell, etc. It should not matter which HBA we use either. Next major release, or next update release? I believe the fix for bug 455465 may also help fix up this issue, and that's scheduled to be a part of the next update release to RHEL5. If it is at all possible for you to test the 5.4 beta when it is released, that would help clarify whether this bug is also taken care of. If not, we will have to decide how to proceed with this bug report. You mentioned RHEL6. We can't wait for RHEL6. I would be happy to test this immediately if you can point me to 5.4 beta. It has not yet been released. Greg, the 5.4 code freeze is next Thursday. We typically create a relatively-untested Alpha and sanity-check it internally, apply bugfixes, and that is what becomes the Beta. Does your company have a TAM? If so, we can maybe get the Alpha to him/her as we do with our hardware partners. Yes, we have a TAM. I've opened a case and asked him to look into getting me this release to test. Moving to RHEL 5.5 so it doesn't get mistakenly closed by the bot. But the Beta is now available - Greg, Robert Proffitt should be able to get it for you. |