Bug 1049243

Summary:	[Neutron integration] Hide incompatible Clusters when adding an external network
Product:	[oVirt] ovirt-engine	Reporter:	GenadiC <gcheresh>
Component:	General	Assignee:	Barak <bazulay>
Status:	CLOSED EOL	QA Contact:	GenadiC <gcheresh>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	---	CC:	bazulay, bugs, ecohen, gcheresh, gklein, lpeer, masayag, mgoldboi, mkolesni, nyechiel, rbalakri, Rhev-m-bugs, sbonazzo, yeylon, ylavi
Target Milestone:	---	Flags:	sbonazzo: needinfo?
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	network
Fixed In Version:	ovirt-3.5.0-alpha1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-02 10:36:23 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:
Bug Depends On:
Bug Blocks:	1063716

Description GenadiC 2014-01-07 09:34:41 UTC

Description of problem:
If you try to create a new network on RHEVM and on External Network provider with incompatible Cluster version you get an error message that the Cluster version is not supported, though the network is created in DC and External Provider

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


How reproducible:
Always

Steps to Reproduce:
1. Try to create a new network for DC and Cluster ver 3.2 and check External provider checkbox to create it on Neutron as well
2.
3.

Actual results:
You get an error message that the Cluster version is not supported.
Though the network was created on Neutron and on the DC

Expected results:
Instead of getting an error message it should get the message in Event log

Additional info:

Comment 1 Moti Asayag 2014-02-12 12:59:48 UTC

Mike, 

Should the supported cluster levels be restricted for the neutron integration ?

Comment 2 Moti Asayag 2014-02-16 13:18:54 UTC

(In reply to Moti Asayag from comment #1)
> Mike, 
> 
> Should the supported cluster levels be restricted for the neutron
> integration ?

Replying to myself, based on discussion with Mike:

The UI should disable adding the network in the unsupported clusters. The action should be blocked as well in the backend by a can-do-action.

We rely on the same vdsm version which the vdsm-hook-openstack is delivered with to examine the cluster level (>= 3.3).

Comment 3 Nir Yechiel 2014-02-19 12:08:11 UTC

Instead of disable it for unsupported clusters, let's just show the relevant clusters.

Comment 4 Sandro Bonazzola 2014-05-08 13:56:40 UTC

This is an automated message.

oVirt 3.4.1 has been released.
This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed.

Comment 5 GenadiC 2014-06-24 14:18:25 UTC

At this stage there is no support for blocking this action in the backend by a can-do-action.
We should test it when there will be support of API

Comment 6 Lior Vernia 2014-06-24 14:22:54 UTC

Changed GUI to mark unsupported clusters as disabled (rather than hide them), as it is more consistent from a UX point of view (think of a user that visits the clusters tab, then goes back to the general tab and marks the checkbox, then goes back to the clusters tab only to find some of them have disappeared).

Per Genadi's comment, pushing back to 3.6, which might include REST API for providers.

Comment 7 Sandro Bonazzola 2015-09-04 09:03:10 UTC

This is an automated message.
This Bugzilla report has been opened on a version which is not maintained anymore.
Please check if this bug is still relevant in oVirt 3.5.4.
If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution)
If it's an RFE please update the version to 4.0 if still relevant.

Comment 8 Sandro Bonazzola 2015-10-02 10:36:23 UTC

This is an automated message.
This Bugzilla report has been opened on a version which is not maintained
anymore.
Please check if this bug is still relevant in oVirt 3.5.4 and reopen if still
an issue.