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

Bug 1647092

Summary:	[RFE] enable the possibility to rename the label of a network without the need to detach it from active hosts
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Simone Tiraboschi <stirabos>
Component:	ovirt-engine	Assignee:	Nobody <nobody>
Status:	CLOSED DUPLICATE	QA Contact:	Michael Burman <mburman>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.7	CC:	aperotti, danken, ratamir, Rhev-m-bugs, stirabos
Target Milestone:	ovirt-4.3.0	Keywords:	FutureFeature
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:	2018-12-21 08:31:42 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:
Bug Depends On:
Bug Blocks:	1417161

Description Simone Tiraboschi 2018-11-06 16:30:51 UTC

Description of problem:
Enable the possibility to rename the label of a network without the need to detach it from active hosts.
We don't have anymore a direct 1:1 link between the logical network name and the name of the bridge on host side but changing the logical network name (label) on engine side without detaching it from active hosts is still not allowed (the user receives an error message).

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. try to change the name of a logical network attached to active hosts
2.
3.

Actual results:
Error message

Expected results:
The user is allowed to change the network label, the bridge name on host side could (should?) remain the same.

Additional info:

Comment 1 Dan Kenigsberg 2018-11-15 22:56:13 UTC

Am I right that this is a dup of bug 1121101 ?

Comment 3 Dan Kenigsberg 2018-12-21 08:31:42 UTC

Please reopen if I am mistaken.

*** This bug has been marked as a duplicate of bug 1121101 ***