Bug 1121101 - [RFE][RHEV] Editable logical network name
Summary: [RFE][RHEV] Editable logical network name
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.4.0
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Michael Burman
URL:
Whiteboard: sync-to-jira
: 1647092 (view as bug list)
Depends On:
Blocks: 1417161 1502204
TreeView+ depends on / blocked
 
Reported: 2014-07-18 11:09 UTC by Evgheni Dereveanchin
Modified: 2022-03-13 13:54 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-11 07:39:32 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:
nyechiel: Triaged+


Attachments (Terms of Use)
RHV-vlans (10.11 KB, image/png)
2017-06-06 09:57 UTC, Sachin
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 655523 0 None None None Never

Description Evgheni Dereveanchin 2014-07-18 11:09:52 UTC
Description of problem:
At the moment, it is only possible to rename virtual networks only when no VMs are using it since the name is uesd directly on hosts to create bridges. This RFE is to enable this kind of editing. This may be achieved for example by separating user-visible virtual network names from bridge names on hosts (use IDs instead?)

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

How reproducible:
always

Steps to Reproduce:
log in to rhev-m
go to networks tab
select a network with attached VMs
right-click
press edit
change the name
press OK

Actual results:
error is displayed:

Error while executing action: Cannot edit Network. Several virtual machines (1) are using this logical network:
VM1
- Please remove it from all virtual machines that are using it and try again.

Expected results:
network renamed successfully

Additional info:

Comment 2 Dan Kenigsberg 2014-07-22 10:13:27 UTC
http://www.ovirt.org/Features/Unrestricted_Network_Names would allow that.

Comment 9 Alistair Ross 2017-02-27 01:19:38 UTC
Is there any chance this can be implemented in a release soon?

Comment 16 Sachin 2017-06-06 09:57:29 UTC
Created attachment 1285322 [details]
RHV-vlans

Comment 17 Yaniv Lavi 2017-10-18 07:48:12 UTC
We will add the ability to make networks name editable in new networks or for existing networks. There is no way to revert to non-editable after this is enabled. The default will stay as non-editable since the majority of cases do not require this and non-editable is more debug friendly.
Bridge name should be available in GUI and API.

Comment 18 Dan Kenigsberg 2017-10-23 08:59:36 UTC
I am unhappy with the request of modifying editability of host-attached networks. Doing so would necessary lead to a network named "new net" while on the hosts it is named "old net" rather than onXXXXX, which I find confusing.

Comment 20 spower 2018-07-03 10:48:23 UTC
We agreed to remove RFEs component from Bugzilla, if you feel the component has been renamed incorrectly please reach out.

Comment 22 Dan Kenigsberg 2018-12-21 08:31:42 UTC
*** Bug 1647092 has been marked as a duplicate of this bug. ***

Comment 24 Dan Kenigsberg 2019-02-26 12:14:38 UTC
Martin Marina and Dominik seems content with the following.
When a new network is created, we would show an Editable checkbox next to it.

As long as the network name is Latin-only and short, the checkbox is off by default. However, the user CAN turn it off, signifying that s/he is fine with onXXXXX bridge names.

If the network is long or has fancy chars, the checkbox is on and cannot be turned off.

Comment 25 Dan Kenigsberg 2019-02-26 12:15:42 UTC
The EditableName boolean should be exposed by REST, validated on input, and stored in the DB.

Comment 27 Michal Skrivanek 2020-06-23 12:34:04 UTC
This request is not currently committed to 4.4.z, moving it to 4.5

Comment 32 Martin Perina 2021-03-11 07:39:32 UTC
We are not putting any more effort into CloudForms, this product has been put into Maintenance. If customer still requires this feature, he need to open an RFE to IBM, who took over of future ManageIQ productization.


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