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:
*** Bug 1506130 has been marked as a duplicate of this bug. ***
Created attachment 1343119 [details] engine and ovirt-provider-ovn logs
Created attachment 1347077 [details] reproduce
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.
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?
> 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.
Please reopen if this reproduces.