Bug 642553

Summary:	Provisioning of KVM domU reboots host system
Product:	Red Hat Satellite 5	Reporter:	Alexander Todorov <atodorov>
Component:	Provisioning	Assignee:	Justin Sherrill <jsherril>
Status:	CLOSED NOTABUG	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	540	CC:	cperry
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	643059 (view as bug list)		Environment:
Last Closed:	2010-10-14 14:21:23 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:	487677

Description Alexander Todorov 2010-10-13 10:22:26 UTC

Description of problem:
Provisioning of KVM domU will reboot host system. See steps to reproduce for details

Version-Release number of selected component (if applicable):
RHN Satellite release 5.4.0

How reproducible:


Steps to Reproduce:
1. Start with a system which has RHEL 5.5 Server. Register it to the satellite, assign the Provisioning and Virtualization Platform entitlements, subscribe to appropriate channels and do yum update.
2. Configure a br0 bridge to use for virtualization networking. Install KVM, libvirt, etc.
3. Reboot. 
4. Create a KS profile with Virtualization type of KVM Guest and @base package set. Fill in the rest of the installation details as well. 
5. From the webUI select the host. Under the Provisioning tab select the KVM domU kickstart profile and schedule the action.
6. Run rhn_check -vv on the host. 

Actual results:
After rhn_check exits the system will reboot in 3 minutes. I canceled the reboot. grub.conf was updated so that it points to a new entry which will re-install the system.

Expected results:
No reboot, new virtual guest is started or appropriate error message is given if something went wrong.

Additional info:

Comment 2 Clifford Perry 2010-10-14 14:21:23 UTC

Hi there, 
the steps to reproduce - that was the correct end result and expected. 

It seems like you are wanting to create/provision new guests. This is done under the Virtualization > Provisioning tab for creating new guests. 

The main provisioning tab will attempt to reinstall the system. 

Cliff