Bug 1124392

Summary:	Attaching/Detaching two (or more) networks with lables to a cluster fails
Product:	[Retired] oVirt	Reporter:	Alona Kaplan <alkaplan>
Component:	ovirt-engine-core	Assignee:	Alona Kaplan <alkaplan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Martin Pavlik <mpavlik>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	3.5	CC:	ecohen, gklein, iheim, mpavlik, rbalakri, yeylon
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	network
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-17 12:22:27 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:

Description Alona Kaplan 2014-07-29 12:06:39 UTC

Description of problem:

Attching/Detaching two (or more) networks with lables to a cluster fails with the following exception-

2014-07-29 14:55:36,866 ERROR [org.ovirt.engine.core.bll.CommandsFactory] (org.ovirt.thread.pool-8-thread-10) Cant find constructor for type org.ovirt.engine.core.bll.network.cluster.DetachNetworksFromClusterCommand with parameter types: [class org.ovirt.engine.core.common.action.ClusterNetworksParameters]


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


How reproducible:
100%

Steps to Reproduce:
1. Add net1 with label lbl1
2. Add net2 with label lbl2
3. Go to cluster->network tab, open manage naetworks dialog
4. Mark both of the networks as attached a click ok

Actual results:
The networks are not attached.
(Same bug with detach).


Expected results:
The networks are attached to the cluster.


Additional info:

Comment 1 Martin Pavlik 2014-09-03 14:27:51 UTC

VERIFIED 
oVirt Engine Version: 3.5.0-0.0.master.20140821064931.gitb794d66.el6 
both attach and detach work ok

Comment 2 Sandro Bonazzola 2014-10-17 12:22:27 UTC

oVirt 3.5 has been released and should include the fix for this issue.