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

Bug 583093

Summary:	VM universe: default bridge interface must exist
Product:	Red Hat Enterprise MRG	Reporter:	Luigi Toscano <ltoscano>
Component:	Grid_User_Guide	Assignee:	Lana Brindley <lbrindle>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jeff Needle <jneedle>
Severity:	medium	Docs Contact:
Priority:	low
Version:	Development	CC:	mhideo
Target Milestone:	1.3
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-10-14 20:01: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:	543560

Description Luigi Toscano 2010-04-16 16:35:03 UTC

Description of problem:
The default XML helper command for VM universe (libvirt_simple_script.awk), when the networking with bridging is enabled, configure the VM to use "br0" as the bridging interface. If such interface does not exist, the job fails (it moves to the "Hold" state).
Even if that parameter is made configurable, sysadmin must be aware that they have to configure that interface.
This information should be documented.

Comment 1 Lana Brindley 2010-06-16 01:54:27 UTC

Added admonition to the Virtual Machine Universe chapter:

<important>
	<para>
		When networking with bridging is enabled, the virtual machine must be ocnfigured to use <parameter>br0</parameter> as the bridging interface. If the <parameter>br0</parameter> bridge does not exist, the job will fail and be moved to the <parameter>hold</parameter>.
	</para>
</important>

LKB