Bug 700802 - 'clearpart --all --initlabel' clears all partitions when using cciss devices with 'ignoredisk --only-use=cciss/c0d0'
Summary: 'clearpart --all --initlabel' clears all partitions when using cciss devices ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda
Version: 5.6
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Chris Lumens
QA Contact: Release Test Team
URL:
Whiteboard:
: 687976 (view as bug list)
Depends On:
Blocks: 726828
TreeView+ depends on / blocked
 
Reported: 2011-04-29 12:56 UTC by William Gomeringer
Modified: 2018-11-14 14:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-24 11:05:27 UTC
Target Upstream Version:


Attachments (Terms of Use)
Kickstart file the customer is using (8.83 KB, application/octet-stream)
2011-04-29 12:57 UTC, William Gomeringer
no flags Details

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.


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