Bug 700802

Summary: 'clearpart --all --initlabel' clears all partitions when using cciss devices with 'ignoredisk --only-use=cciss/c0d0'
Product: Red Hat Enterprise Linux 5 Reporter: William Gomeringer <wgomerin>
Component: anacondaAssignee: Chris Lumens <clumens>
Status: CLOSED WONTFIX QA Contact: Release Test Team <release-test-team>
Severity: high Docs Contact:
Priority: high    
Version: 5.6CC: ablum, atodorov, jwest, mollo, rmunilla
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-24 11:05:27 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
Kickstart file the customer is using none

Description William Gomeringer 2011-04-29 12:56:51 UTC 
Description of problem:
In kickstart:
clearpart --all --initlabel
ignoredisk --only-use=cciss/c0d0

clears the partition table

we tested this with:
clearpart --all --initlabel
ignoredisk --only-use=vda

and it did not clear the partition table. 

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

How reproducible:
Always

Steps to Reproduce:
1. Use the following in your kickstart file with a cciss devices
clearpart --all --initlabel
ignoredisk --only-use=cciss/c0d0

2. Then test with another device, for example 
clearpart --all --initlabel
ignoredisk --only-use=vda

3. In the second example device 'vda' is ignored. This is not the case when specifying a cciss device
  
Actual results:
Device 'vda' is ignored. This is not the case when specifying a cciss device

Expected results:
Device 'cciss/c0d0' should be ignored

Additional info:
The customer is reluctant to try anything else at this point, and I do not have access to a cciss device to test this. Is the proper syntax:
clearpart --all --initlabel
ignoredisk --only-use=c0d0

-or-

clearpart --all --initlabel
ignoredisk --only-use=cciss

instead of using cciss/c0d0?
Comment 1 William Gomeringer 2011-04-29 12:57:35 UTC 
Created attachment 495772 [details]
Kickstart file the customer is using
Comment 5 David Cantrell 2011-08-09 21:39:52 UTC 
*** Bug 687976 has been marked as a duplicate of this bug. ***
Comment 6 Chris Lumens 2011-08-22 15:44:49 UTC 
Sorry, I'm finding the initial comment very difficult to follow.  Can you restate the problem more clearly?  Does the attached kickstart file come from a system exhibiting the problem?  When you hit this problem, is it on a system with both CCISS devices and a vda device?  Or is the problem only happening if the kickstart file references devices that do not exist?

Can you also attach /tmp/anaconda.log to this bug report after you hit the problem?

The correct syntax for anything involving CCISS is "cciss/cXdX".
Comment 7 Alexander Todorov 2011-08-24 10:45:53 UTC 
Tested on RHEL 5.7 on systems with 2 disks:

1) Tested on KVM guest:

clearpart --all --initlabel
ignoredisk --only-use=vda
autopart

Only disk vda was used during install. Disk vdb wasn't touched and the data on it was intact.


2) Tested on bare metal hardware with 2 cciss disks:

clearpart --all --initlabel
ignoredisk --only-use=cciss/c0d0
autopart

disk c0d1 wasn't touched and data on it was intact. 


I can't reproduce.
Comment 8 RHEL Program Management 2011-08-24 11:05:27 UTC 
Quality Engineering Management has reviewed and declined this request.  You may
appeal this decision by reopening this request.