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

Bug 1085819

Summary: "Failed to attach network to Cluster" error message when trying to create new network with label that used to be on Bond
Product: Red Hat Enterprise Virtualization Manager Reporter: GenadiC <gcheresh>
Component: ovirt-engineAssignee: Lior Vernia <lvernia>
Status: CLOSED CURRENTRELEASE QA Contact: GenadiC <gcheresh>
Severity: high Docs Contact:
Priority: medium    
Version: 3.4.0CC: bazulay, danken, gklein, iheim, lpeer, lvernia, masayag, myakove, rbalakri, Rhev-m-bugs, sherold, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: vt1.3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:07:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine log none

Description GenadiC 2014-04-09 12:47:03 UTC
Created attachment 884498 [details]
engine log

Description of problem:
If you create a bond and put on it label xxx and then break that bond, that label is not removed from the system.
As a result creating a new network with label xxx will produce error message that the network couldn't be added to Cluster and in engine VdcBLLException: LABELED_NETWORK_INTERFACE_NOT_FOUND (Failed with error LABELED_NETWORK_INTERFACE_NOT_FOUND and code 5200)

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


How reproducible:
Always

Steps to Reproduce:
1. Create bond with label xxx
2. Break that bond, so that label will disappear
3. Create new Network with label xxx

Actual results:
You get LABELED_NETWORK_INTERFACE_NOT_FOUND error message in log and error message in GUI that the network couldn't be added to Cluster

Expected results:
Network should be created without any issue

Additional info:

Comment 1 Lior Vernia 2014-04-17 13:51:52 UTC
This happens because the engine doesn't persist the wiping of labels for bonds being removed, and VDSM seems to report bonds even if they don't have networks attached to them anymore (they're not being torn down).

Modifying either of these two behaviors should solve the bug; I'm just not sure which would be better.

Comment 2 Dan Kenigsberg 2014-04-17 14:41:52 UTC
bond0 to bond4 are not torn down due to backward compatibility with engine-3.0 which expects to always see them.

Tearing down a bond may fail on other cases (such as if the bond is being used by something outside of oVirt).

Labels are Engine-only constructs. If a label is not used by any other Engine entity, it should evaporate.

Comment 3 Dan Kenigsberg 2014-05-08 07:36:41 UTC
This bug is not a blocker or an exception forand won't make it for 3.4.0.

Comment 4 Lior Vernia 2014-05-08 10:50:37 UTC
I suggest that we do backport this with an exception, I think it's bad enough.

Comment 6 Alona Kaplan 2014-06-16 08:45:08 UTC
*** Bug 1109706 has been marked as a duplicate of this bug. ***

Comment 7 Alona Kaplan 2014-06-16 09:06:12 UTC
*** Bug 1109706 has been marked as a duplicate of this bug. ***

Comment 8 GenadiC 2014-07-16 14:01:28 UTC
Verified in ovirt-engine-3.5.0-0.0.master.20140715172116.git4687dc1.el6.noarch

Comment 9 Eyal Edri 2015-02-17 17:07:04 UTC
rhev 3.5.0 was released. closing.