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

Bug 1506131

Summary: When setting a specific cluster to be OVN type, all clusters become OVN type
Product: [oVirt] ovirt-provider-ovn Reporter: Mor <mkalfon>
Component: providerAssignee: Dominik Holler <dholler>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Mor <mkalfon>
Severity: high Docs Contact:
Priority: high    
Version: 1.0.4CC: bugs, danken, mkalfon, ylavi
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-08 12:19:37 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 and ovirt-provider-ovn logs
none
reproduce none

Description Mor 2017-10-25 08:39:57 UTC 
Description of problem:
When selecting a specific cluster to be OVN type, all other clusters are affected by this setting.

Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20171020191516.gitff33cdc.el7.centos
ovirt-provider-ovn-1.2-0.20171020111522.git3dd43cf.el7.centos.noarch

How reproducible:
100%

Steps to Reproduce:
At least 2 clusters are needed to reproduce.
1. Edit existing cluster and set 'Default Network Provider' to be 'ovirt-provider-ovn' (the default OVN provider created by engine-setup).
2. Edit another existing non-OVN cluster, and check the 'Default Network Provider' value.

Actual results:
All non-OVN clusters becomes OVN clusters.

Expected results:
Only the specific cluster should become OVN cluster.

Additional info:
Comment 1 Mor 2017-10-25 08:40:50 UTC 
*** Bug 1506130 has been marked as a duplicate of this bug. ***
Comment 2 Mor 2017-10-25 08:43:26 UTC 
Created attachment 1343119 [details]
engine and ovirt-provider-ovn logs
Comment 3 Dominik Holler 2017-11-02 16:53:31 UTC 
Created attachment 1347077 [details]
reproduce
Comment 4 Dominik Holler 2017-11-02 16:57:01 UTC 
I am not able to reproduce the behavior. Neither in the UI nor via the REST-API (see attachment 1347077 [details]).
Maybe the second cluster was changed by engine-setup?

Currently, engine-setup assigns the default provider to clusters without default provider. But this behavior seems to be unexpected and should be changed.
Comment 5 Mor 2017-11-02 20:45:07 UTC 
Not sure what exactly has changed between versions, but I am unable to reproduce it on later oVirt version: 4.2.0-0.0.master.20171030210714.gitef6bb9c.el7.centos.

Does engine-setup assigns the default provider to all clusters during upgrade? What if the user wishes to not install OVN? Or wish to select which cluster supports OVN?
Comment 6 Dominik Holler 2017-11-02 20:50:02 UTC 
> Does engine-setup assigns the default provider to all clusters during upgrade?

Currently to all clusters without a provider.

> What if the user wishes to not install OVN?

In this case, no provider is assigned.

> Or wish to select which cluster supports OVN

I think of changing it in a way that the provider is assigned only to the default cluster.
Comment 7 Dan Kenigsberg 2017-11-08 12:19:37 UTC 
Please reopen if this reproduces.