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.

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:

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

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

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

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

(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.

(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.

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

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