Bug 842948

Summary:	oVirt 3.1 - breth0 still available after registration and manual reboot
Product:	[Retired] oVirt	Reporter:	Douglas Schilling Landgraf <dougsland>
Component:	vdsm	Assignee:	Douglas Schilling Landgraf <dougsland>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.1 RC	CC:	abaron, acathrow, bazulay, dyasny, iheim, mgoldboi, oschreib, ykaul
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	network
Fixed In Version:	vdsm-4.10.0-6.fc17	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	845346 (view as bug list)		Environment:
Last Closed:	2012-08-01 14:10:02 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:	822145, 845346

Description Douglas Schilling Landgraf 2012-07-25 04:12:20 UTC

Description of problem:

oVirt Node register correctly in oVirt Engine. When a reboot is executed manually in the node breth0 is still in the system (ovirtmgmt as well).

Version-Release number of selected component (if applicable):
http://www.ovirt.org/releases/beta/binary/ovirt-node-iso-2.5.0-2.0.fc17.iso

How reproducible:

Steps to Reproduce:
1. Install oVirt Node
2. Setup Network 
3. Approve the Node in oVirt Engine and wait it became UP
4. Reboot manually the node.

Actual results:
After reboot the node stopped to communicate with ovirt Engine, requiring ifdown breth0.

Expected results:
Remove breth0 during the deploy.

Comment 1 Douglas Schilling Landgraf 2012-07-26 01:27:46 UTC

Patch available:
http://gerrit.ovirt.org/#/c/6634/