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

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.

Bug 856710

Summary:

3.1 - host losses connectivity when moving rhevm network from one interface to another (rollback doesn't work)

Product:

Red Hat Enterprise Linux 6

Reporter:

Ondra Machacek <omachace>

Component:

vdsm

Assignee:

Igor Lvovsky <ilvovsky>

Status:

CLOSED DUPLICATE

QA Contact:

GenadiC <gcheresh>

Severity:

urgent

Docs Contact:

Priority:

high

Version:

6.3

CC:

abaron, bazulay, danken, hateya, iheim, jhenner, lpeer, mavital, sgrinber, ykaul

Target Milestone:

Keywords:

ZStream

Target Release:

---

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

network

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2012-09-23 14:48:51 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:

Attachments:

Description	Flags
vdsm.log	none

Description Ondra Machacek 2012-09-12 15:55:33 UTC

Description of problem:


Version-Release number of selected component (if applicable):
vdsm-4.9.6-31.0.el6_3

How reproducible:
always

Steps to Reproduce:
1. Have rhevm on em1(up) and have rhevm bridge on it. And have em2(no_carrier) and without rhevm bridge on it.
2. Try to assign rhevm bridge from em1 to em2. Have 'Verify connectivity between Host and Engine' checked and 'Save network configuration' checked. Click OK.
  
Actual results:
rhevm <=> vdsm connection breaks.

Expected results:
Error message: this action should destroy connection, do rollback.

Additional info:

Comment 2 Jaroslav Henner 2012-09-12 16:09:25 UTC

Expected results should be:
Error message: this action would destroy connection, doing roll-back.

Comment 3 Dan Kenigsberg 2012-09-13 19:35:57 UTC

please attach relevant vdsm.log. I would very much request a reproduction with vdsm-4.9.6-34.0 that has better logging.

Comment 4 Ondra Machacek 2012-09-14 07:55:01 UTC

Created attachment 612770 [details]
vdsm.log

Comment 5 GenadiC 2012-09-23 12:01:54 UTC

From the tests we performed on SI18 it looks like the problem happens only for DHCP (rollback on static IP for rhevm network worked fine).
As well the problem is not seen anymore (even on DHCP configuration) after testing http://gerrit.ovirt.org/#/c/8058/ that fixes the https://bugzilla.redhat.com/show_bug.cgi?id=857112
We'll need to verify it in the next release when that fix will be merged.

Comment 6 Dan Kenigsberg 2012-09-23 14:48:51 UTC

Apparently, the same underlying problem - infecting all ifcfg* files with BOOTPROTO - caused this bug. Therefore, I'm closing it as a duplicate. Please re-open if I am mistaken.

*** This bug has been marked as a duplicate of bug 857112 ***