Bug 1276512 - Kickstart File error with Custom Partitioning for CentOS7
Summary: Kickstart File error with Custom Partitioning for CentOS7
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 2.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space27
TreeView+ depends on / blocked
 
Reported: 2015-10-29 22:20 UTC by Doug
Modified: 2017-09-28 18:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-29 22:26:52 UTC
Embargoed:

Attachments (Terms of Use)

Description Doug 2015-10-29 22:20:13 UTC 
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 22:26:52 UTC 
Found additional partitioning options under "System Details"
Removed offending directives.
Kickstart is now valid
Comment 2 Eric Herget 2017-09-28 18:10:58 UTC 
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.