Bug 1023584

Summary:	cannot get autopart to run after a run through custom storage
Product:	Red Hat Enterprise Linux 7	Reporter:	David Lehman <dlehman>
Component:	anaconda	Assignee:	David Lehman <dlehman>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	anaconda-maint-list, mbanas, mganisin
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	anaconda-19.31.45-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1023554	Environment:
Last Closed:	2014-06-13 09:44:40 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:

Description David Lehman 2013-10-25 20:22:09 UTC

+++ This bug was initially created as a clone of Bug #1023554 +++

Description of problem:
If you go through and create a layout in the custom spoke and then revisit storage and try to do autopart with reclaim it doesn't ever set the autopart flag.

Version-Release number of selected component (if applicable):
anaconda-19.31.30-1

How reproducible:
Always

Steps to Reproduce:
1. select one of two full disks, go to custom, clear it, autopart, save it
2. revisit storage, select both disks, choose to reclaim, delete all
3. click "Reclaim"

Actual results:
disks are reinitialized but autopart is not run

Expected results:
disks initialized and autopart run

Additional info:
Nothing is setting self.autopart to True in the storage spoke in this case

Comment 3 Ludek Smid 2014-06-13 09:44:40 UTC

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.