RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ 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/

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

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

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