Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1276512

Summary:	Kickstart File error with Custom Partitioning for CentOS7
Product:	[Community] Spacewalk	Reporter:	Doug <doug.hunting>
Component:	Server	Assignee:	Tomas Lestach <tlestach>
Status:	CLOSED NOTABUG	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.4	CC:	doug.hunting
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-29 22:26:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1484117

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.