Bug 453167 - Kickstart fails with pre-defined disk partitions
Kickstart fails with pre-defined disk partitions
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: pyparted (Show other bugs)
x86_64 Linux
low Severity high
: rc
: ---
Assigned To: David Cantrell
Depends On:
  Show dependency treegraph
Reported: 2008-06-27 13:03 EDT by Cris Rhea
Modified: 2008-11-11 17:37 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-11 17:34:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Sample, simplified Kickstart file to demonstrate issue. (896 bytes, text/plain)
2008-06-27 13:03 EDT, Cris Rhea
no flags Details

  None (edit)
Description Cris Rhea 2008-06-27 13:03:21 EDT
Description of problem:

Using a kickstart file where the disk is pre-partitioned (in the %pre section)
fails with the error:

Error informing the kernel about modifications to partition /dev/sda5 -- Device
or resource busy.

Version-Release number of selected component (if applicable):
No clue. I would have put this in "Kickstart", but it's not listed in the
drop-down list. If pyparted is not the correct component, please let me know
where to move this.

How reproducible:

Every time.

Steps to Reproduce:
1. Use sample attached Kickstart file to attempt to load system. 
   Net boot from CD or use PXEboot (whatever convenient).

2. System will fail and display error message.
Actual results:

Kickstart install fails with above error. This has worked for years
(since at least RH7). Started failing between RHEL/CentOS 4.4 and 4.5.

The %pre section does work as expected (disk is physically partitioned correctly).

The blockdev and partprobe commands were added based on suggestions-- they were
never required previously.

Expected results:

Kickstart puts specified file systems on existing partitions.

Additional info:
Comment 1 Cris Rhea 2008-06-27 13:03:21 EDT
Created attachment 310461 [details]
Sample, simplified Kickstart file to demonstrate issue.
Comment 2 David Cantrell 2008-11-11 17:34:24 EST
We're addressing issues like this one in Fedora first.  If this is an issue for your RHEL installation, please contact Red Hat technical support and have the issue escalated through our support channels.


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