Bug 836954

Summary:	3.1- Allow to break bond and create a new network on its interface in single action
Product:	Red Hat Enterprise Linux 6	Reporter:	Igor Lvovsky <ilvovsky>
Component:	vdsm	Assignee:	Igor Lvovsky <ilvovsky>
Status:	CLOSED ERRATA	QA Contact:	Meni Yakove <myakove>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	abaron, bazulay, cpelland, danken, iheim, lpeer, mkenneth, ykaul
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	Network
Fixed In Version:	vdsm-4.9.6-21	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-04 19:01:56 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:

Description Igor Lvovsky 2012-07-02 10:10:19 UTC

Description of problem:

Assume we have a bond0 on (eth1, eth2) with defined network brNet on it.
This patch will allow to break the bond0 and create a new network brNet2 on one
of its interfaces (e.g. eth2) with single setupNetworks operation

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Yaniv Kaul 2012-07-02 15:41:25 UTC

How do we test this? Will it be available via REST (from RHEVM) in a single action?

Comment 2 Igor Lvovsky 2012-07-02 15:45:54 UTC

First, you can easly test it from UI.
Don't know about REST, but it should be supported as every setupNetworks action

Comment 3 Igor Lvovsky 2012-07-02 15:51:07 UTC

http://gerrit.ovirt.org/#/c/5841/

Comment 4 Yaniv Kaul 2012-07-02 15:54:24 UTC

Dan, shouldn't this be proposed to 6.4 as well?

Comment 5 Dan Kenigsberg 2012-07-02 16:05:42 UTC

(In reply to comment #4)
> Dan, shouldn't this be proposed to 6.4 as well?

If it's in rhel-6.3.z, it means that it is upstream, which means that it would be in rhel-6.4 by virtue of the pending 6.4 rebase. I do not see any point of a 6.4-specific bug.

Comment 7 Yaniv Kaul 2012-07-02 16:34:58 UTC

(In reply to comment #5)
> (In reply to comment #4)
> > Dan, shouldn't this be proposed to 6.4 as well?
> 
> If it's in rhel-6.3.z, it means that it is upstream, which means that it
> would be in rhel-6.4 by virtue of the pending 6.4 rebase. I do not see any
> point of a 6.4-specific bug.

To ensure it's being tested in 6.4.

Comment 10 Meni Yakove 2012-07-23 11:51:29 UTC

Verified on vdsm-4.9.6-23.0.el6_3.x86_64.

Comment 13 errata-xmlrpc 2012-12-04 19:01:56 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