Bug 687976

Summary: ignoredisk ks option breaks clearpart behavior
Product: Red Hat Enterprise Linux 5 Reporter: Dustin Mollo <mollo>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6CC: eric.eisenhart
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-09 21:39:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 726828    
Attachments:
Description Flags
RHEL 5.6 partitioning config section
none
RHEL 6 partitioning config section
none
anaconda installer log
none
syslog output from failed 5.6 install none

Description Dustin Mollo 2011-03-15 21:40:56 UTC
Description of problem:
When you add an ignoredisk option (ignoredisk --only-use=sda,cciss/c0d0) to a kickstart that also contains "clearpart --all --initlabel", it causes anaconda to fail to skip read-only media (ie, CD-ROM devices) and prompts for human interaction during, which should be, an automated install.

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

Additional info:

It looks like the problem code lives in partedUtils.py:

        for drive in self.driveList():
            # ignoredisk takes precedence over clearpart (#186438).
            if (DiskSet.exclusiveDisks != [] and drive not in DiskSet.exclusiveDisks) or drive in DiskSet.skippedDisks:
                continue
            deviceFile = isys.makeDevInode(drive, "/dev/" + drive)
            if not isys.mediaPresent(drive) or isys.deviceIsReadOnly(drive):
                self._removeDisk(drive)
                continue

Comment 1 Chris Lumens 2011-03-16 17:14:40 UTC
Do you still see this problem with RHEL6?

Comment 2 Dustin Mollo 2011-03-16 18:05:37 UTC
I applied the same change to our RHEL 6 ks environment and I get completely different, yet still broken behavior. In RHEL 6 anaconda dies saying that the system does not have a cciss/c0d0 device. The only major difference between our 5.6 and 6 partitioning sections is the specification of ext4 on RHEL 6 instead of ext3. I'll attach the two partitioning blocks to the bug report.

Comment 3 Dustin Mollo 2011-03-16 18:07:14 UTC
Created attachment 485807 [details]
RHEL 5.6 partitioning config section

Comment 4 Dustin Mollo 2011-03-16 18:07:35 UTC
Created attachment 485808 [details]
RHEL 6 partitioning config section

Comment 5 Dustin Mollo 2011-03-18 17:00:12 UTC
I have a support ticket open on this issue as well. They asked for the anaconda and syslog files. I'm going to upload them here as well.

Comment 6 Dustin Mollo 2011-03-18 17:00:37 UTC
Created attachment 486281 [details]
anaconda installer log

Comment 7 Dustin Mollo 2011-03-18 17:00:57 UTC
Created attachment 486282 [details]
syslog output from failed 5.6 install

Comment 9 David Cantrell 2011-08-09 21:39:52 UTC

*** This bug has been marked as a duplicate of bug 700802 ***