Bug 1055188

Summary: [NetworkLabels] Detaching two labeled networks from a cluster result in failure of the latter
Product: [Retired] oVirt Reporter: Moti Asayag <masayag>
Component: ovirt-engine-coreAssignee: Moti Asayag <masayag>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Pavlik <mpavlik>
Severity: high Docs Contact:
Priority: high    
Version: 3.4CC: acathrow, gklein, iheim, mpavlik, myakove, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: ovirt-3.4.0-beta2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-31 12:27:26 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:
Bug Depends On: 1055952    
Bug Blocks: 1024889    

Description Moti Asayag 2014-01-19 13:50:55 UTC
Description of problem:
When multiple labeled networks are being detached from a single cluster, a sequential setup networks requests per each network are being sent to the host in order to remove the labeled network from the labeled interface.
As a result, the latter 'setup networks' requests fail with the vdsm agent unavailability to serve the them.
 
The engine should construct a single request with the expected network configuration and to send it to vdsm.

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


How reproducible:
always

Steps to Reproduce:
1. Label 2 networks which are attached to a cluster and configured on a label nic.
2. From the webmain, cluster ---> manage networks --> uncheck those 2 networks and click 'ok'.

Actual results:
The first network is being removed and the second network remain with an error to the engine log stating : "resource unavailable"

Expected results:
Both networks should be removed from the host, preferably in a single request.

Comment 1 Martin Pavlik 2014-02-12 13:27:53 UTC
works in  oVirt Engine Version: 3.4.0-0.7.beta2.el6

Comment 2 Sandro Bonazzola 2014-03-31 12:27:26 UTC
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released