Bug 845346

Summary:	oVirt 3.1 - breth0 still available after registration and manual reboot
Product:	Red Hat Enterprise Linux 6	Reporter:	Douglas Schilling Landgraf <dougsland>
Component:	vdsm	Assignee:	Douglas Schilling Landgraf <dougsland>
Status:	CLOSED ERRATA	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.3	CC:	abaron, acathrow, bazulay, cpelland, danken, dyasny, iheim, ilvovsky, lpeer, mgoldboi, oschreib, ykaul
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	network
Fixed In Version:	vdsm-4.9.6-29.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	842948	Environment:
Last Closed:	2012-12-04 19:04:26 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:	842948
Bug Blocks:

Description Douglas Schilling Landgraf 2012-08-02 18:42:00 UTC

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

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.

--- Additional comment from dougsland on 2012-07-25 21:27:46 EDT ---

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

Comment 1 lpeer 2012-08-06 12:26:49 UTC

http://gerrit.usersys.redhat.com/#change,1375

Comment 2 Dan Kenigsberg 2012-08-06 14:09:45 UTC

This ain't an oVirt bug, it should not block ovirt-3.1.

Comment 8 errata-xmlrpc 2012-12-04 19:04:26 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-1508.html