Bug 1276512 - Kickstart File error with Custom Partitioning for CentOS7
Kickstart File error with Custom Partitioning for CentOS7
Status: CLOSED NOTABUG
Product: Spacewalk
Classification: Community
Component: Server (Show other bugs)
2.4
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Tomas Lestach
Red Hat Satellite QA List
:
Depends On:
Blocks: space27
  Show dependency treegraph
 
Reported: 2015-10-29 18:20 EDT by Doug
Modified: 2017-09-28 14:10 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-10-29 18:26:52 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Doug 2015-10-29 18:20:13 EDT
Description of problem:
Spacewalk is automatically adding "autopart --type=lvm" to the kickstart file even with autopart disabled from advanced options tab. This conflicts with a generated custom partitioning scheme that I am putting in the kickstart file

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

How reproducible:
Always

Steps to Reproduce:
1. Create kickstart file
2. Add custom options for partition schema
3. Display kickstart file in Web UI

Actual results:
Kickstart error: cannot define part and autopart

Expected results:
Removal of autopart directive and partition according to custom options

Additional info:
Comment 1 Doug 2015-10-29 18:26:52 EDT
Found additional partitioning options under "System Details"
Removed offending directives.
Kickstart is now valid
Comment 2 Eric Herget 2017-09-28 14:10:58 EDT
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.

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