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.

Created attachment 593234 [details]
engine.log

Description of problem:
I manage to attache the same bridge network to two different interfaces (one interface and one BOND). 

brctl show
bridge name     bridge id               STP enabled     interfaces
rhevm           8000.00145e17d464       no              eth2
test            8000.00145e17d466       no              bond0.100
                                                        eth3.100
test123         8000.00145e17d466       no              bond0.123
                                                        eth3.123
vlan1000        8000.00145e17d466       no              bond0.1000
                                                        eth3.1000
vlan200         8000.00145e17d466       no              bond0.200
                                                        eth3.200


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


How reproducible:
very rare.

Steps to Reproduce:
1.not sure.

  
Actual results:
Got the same bridge interface on two different interfaces

Expected results:
bridge network should be attached to only one interface at the same time.

Created attachment 593235 [details]
vdsm.log

Created attachment 593236 [details]
UI

Steps to Reproduce:

1. create 5 VLAN networks.
2. on SetupNetworks create BOND and add 1 VLAN to it.
3. on SetupNetwork add 4 VLAN's to interface.
4. Apply
5. Open SetupNetwork and drag 1 VLAN form interface to BOND > apply.
6. Open setupNetwork and you should see that the VLAN that we drag are on the interface and on the BOND.

  Meni,
I can't reproduce this.
Please try to reproduce it on our latest vdsm, I want to look at it on the fly.

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

tested with vdsm-4.9.6-24.0.el6_3.x86_64 and can't reproduce it.

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