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

Bug 1583486

Summary: Block renaming/modifying name of external provider
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Dominik Holler <dholler>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: low    
Version: 4.2.3.5CC: bugs
Target Milestone: ovirt-4.2.4Flags: rule-engine: ovirt-4.2+
Target Release: ---   
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: 2018-06-26 08:40:47 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 Michael Burman 2018-05-29 06:10:12 UTC 
Description of problem:
Block renaming/modifying name of external provider.

Currently it's possible to do so via the engine(we have no validation for it) and after the syncCommand the name of the ovn network returns to the origin.

On a DC with two clusters configured with 'ovirt-provider-ovn' as external network provider. If you create OVN network on ovirt-provider-ovn, auto-sync will create two networks, one of each cluster. In case you rename one of the clusters networks, then delete the other cluster network (through UI or the provider directly), both networks will be deleted.

Modifying name of external provider should be done via the provider

The fix only available on master, we would like to backport to 4.2

Version-Release number of selected component (if applicable):
4.2.4-0.1.el7

See also:
https://bugzilla.redhat.com/show_bug.cgi?id=1539765
Comment 2 Michael Burman 2018-06-11 09:32:55 UTC 
Name editing is disabled for external networks in the UI. 

Verified on - 4.2.4.2-0.1.el7_3
Comment 3 Sandro Bonazzola 2018-06-26 08:40:47 UTC 
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.4 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.