Bug 1583486 - Block renaming/modifying name of external provider
Summary: Block renaming/modifying name of external provider
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Hardware: x86_64
OS: Linux
Target Milestone: ovirt-4.2.4
: ---
Assignee: Dominik Holler
QA Contact: Michael Burman
Depends On:
TreeView+ depends on / blocked
Reported: 2018-05-29 06:10 UTC by Michael Burman
Modified: 2018-06-26 08:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-06-26 08:40:47 UTC
oVirt Team: Network
rule-engine: ovirt-4.2+

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
oVirt gerrit 91701 0 ovirt-engine-4.2 MERGED webadmin: Disable changing the name of external networks 2018-06-04 14:31:30 UTC

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):

See also:

Comment 2 Michael Burman 2018-06-11 09:32:55 UTC
Name editing is disabled for external networks in the UI. 

Verified on -

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.

Note You need to log in before you can comment on or make changes to this bug.