Bug 1373477

Summary:	New network that created on external provider is not attached to any cluster in the DC
Product:	[oVirt] ovirt-engine	Reporter:	Michael Burman <mburman>
Component:	BLL.Network	Assignee:	Marcin Mirecki <mmirecki>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Meni Yakove <myakove>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0.4	CC:	bugs, danken, ylavi
Target Milestone:	ovirt-4.1.0-beta	Keywords:	Regression
Target Release:	---	Flags:	ylavi: ovirt-4.1+ ylavi: blocker+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-15 14:50:36 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:

Description Michael Burman 2016-09-06 11:44:02 UTC

Description of problem:
New network created on external provider is not attached to any cluster in the DC and it's not possible to attach it to any cluster(the checkboxes grayed out)

When creating new network on external provider, the 'Attach' to cluster checkboxes got unchecked and grayed out, but they must remain as attached to the cluster/s in the DC. And it's not possible to check the 'Attach' checkbox.
It is means that we can't attach any network that is created on external provider to any cluster in the DC and can't be used to run VM.

On 3.6, the network remain 'Attached' to the cluster/s

Version-Release number of selected component (if applicable):
4.0.4-0.1.el7ev

How reproducible:
100

Steps to Reproduce:
1. Add external provider to rhv-m 4.0.4
2. Create new network and check the 'Create on external provider' checkbox

Actual results:
Network isn't attached to any cluster and it's not possible to attach it to any cluster. The 'Attach All' and 'Attach' checkboxes are grayed out and can't be choosen.

Expected results:
When creating new network on external provider, the network should be attached to all clusters in the DC(but not required)

Comment 1 Dan Kenigsberg 2016-09-06 12:38:38 UTC

In 4.0 we do not support creating external networks from Engine; we only consume them. Still, we have to fix this in master, and consider backporting if it's a quick one.

Comment 2 Red Hat Bugzilla Rules Engine 2016-09-06 12:38:44 UTC

This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 3 Michael Burman 2016-09-06 12:44:00 UTC

(In reply to Dan Kenigsberg from comment #1)
> In 4.0 we do not support creating external networks from Engine; we only
> consume them. Still, we have to fix this in master, and consider backporting
> if it's a quick one.

Yes we have to fix it on master in order to use OVN. Currently i can't assign any 'ovn' network to any cluster in DC and use it by VM.(i have to create it via cmdline and import)

Comment 4 Marcin Mirecki 2016-12-06 11:32:17 UTC

Would attaching to all clusters be the correct behavior?
For external networks not all clusters might be set up for external networks.

Maybe we should stick to no network being attached by default, but allow to attach them (currently this is disabled for external networks)?

Comment 5 Michael Burman 2016-12-06 15:40:07 UTC

Hello Marcin

We believe that the correct behavior is to attach all the networks, including the external networks to all clusters even if not all of them are set up for external provider use. 
Attaching the external networks to all clusters can't cause harm and shouldn't affect the clusters by any way.
This is very useful when you have multiple clusters. 

User should be able to unattach them and edit the checkboxes if he wants.

Comment 6 Marcin Mirecki 2016-12-08 10:52:04 UTC

The fix is available:
http://resources.ovirt.org/repos/ovirt/experimental/master/latest/rpm/el7/noarch/ovirt-engine-4.1.0-0.2.master.20161208091202.git19e6ab3.el7.centos.noarch.rpm

Comment 7 Michael Burman 2016-12-11 10:47:03 UTC

Verified on - 4.1.0-0.2.master.20161210231201.git26a385e.el7.centos

Both scenarios are pass-
[1] - New network created on the external provider attached to all clsuetrs
[2] - Imported network from external provider attached to all clusters