Bug 649697

Summary:	installation stucks on systemid backup
Product:	[Community] Spacewalk	Reporter:	Marcus Moeller <marcus.moeller>
Component:	Server	Assignee:	Michael Mráka <mmraka>
Status:	CLOSED NEXTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.2
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-11-17 09:21:26 UTC	Type:	---
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:	623772

Description Marcus Moeller 2010-11-04 10:30:47 UTC

Description of problem:

We have upgraded our server to v.1.1 and now kickstarting stucks after retrieving install.img. The relevant output in anaconda log is that %pre  scripts are run.

The script that is actively run is the one that backups the old systemid (which contains a loop, which seems to prevent stage2 from being loaded).

Note: kickstarting is possible if no old systemid has been found.

Version-Release number of selected component (if applicable):
1.1

How reproducible:
kickstart a system that already has a systemid file on disk

Comment 1 Marcus Moeller 2010-11-05 11:17:13 UTC

A workaround is to set 'Leave the existing system profile in place, but do not re-connect to it. Instead, create a new system profile.' in System Details of the Kickstart profile

Comment 2 Jan Pazdziora (Red Hat) 2010-11-11 08:10:25 UTC

Mass-aligning under space12, so that we don't lose track of this bugzilla. This
however does not mean that we plan (will be able to) address this bug in
Spacewalk 1.2.

Comment 3 Marcus Moeller 2010-11-17 09:21:26 UTC

Fixed in 1.2 rc by removing the while loop.