Bug 1329893 - UI: explain why we cannot change the logical network settings in the "Manage Networks" window
Summary: UI: explain why we cannot change the logical network settings in the "Manage ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ovirt-4.1.1
: 4.1.1.2
Assignee: Yevgeny Zaspitsky
QA Contact: Meni Yakove
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-24 12:17 UTC by Sharon Gratch
Modified: 2017-04-21 09:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-21 09:53:40 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.1+


Attachments (Terms of Use)
the "Manage Networks" window with the options as radio buttons (51.21 KB, image/png)
2016-04-24 12:17 UTC, Sharon Gratch
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 71817 0 master MERGED webadmin: disable unsetting initally assigned network role 2017-02-12 14:07:11 UTC
oVirt gerrit 72115 0 ovirt-engine-4.1 MERGED webadmin: disable unsetting initally assigned network role 2017-02-12 16:39:42 UTC

Description Sharon Gratch 2016-04-24 12:17:11 UTC
Created attachment 1150153 [details]
the "Manage Networks" window with the options as radio buttons

Description of problem:

Trying to change the logical network settings in the "Manage Networks" window  is impossible when done from the Logical Networks tab in the details pane. The options are displayed as "radio buttons"and once an option is set, it can't be unset.
while opening it from the clusters tab in the details pane - it can be unset but once the wondow is closed and reopened - it is displayed as set again.


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


How reproducible:
consistently


Steps to Reproduce:
1.open the Clusters resource tab and select a cluster in the results list.

2. Select the Logical Networks tab in the details pane to list the logical networks assigned to the cluster.

3. Click "Manage Networks" to open the Manage Networks window. ⁠

4. try to unset/set one of the "Management", "Display Network", "migration network" "gluster network" properties - and see that it's impossible to unset them once set. 


Actual results:
can't unset the logical network options

Expected results:
set/unset the "Management", "Display Network", "migration network" "gluster network" properties should work without any problem.

Additional info:
See Screenshot attached

Comment 1 Red Hat Bugzilla Rules Engine 2016-04-24 12:27:26 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 2 Yevgeny Zaspitsky 2016-04-24 17:25:47 UTC
According to the attached picture there is only one network assigned to the cluster. Each cluster has to have at exactly one network for each role (that is why it's drown as radio-button rather than a check-box). In your case the same network (ovirtmgmt) fulfills all those roles. Once you add another network to the cluster, you'll be able to choose that to implement one or more roles in the cluster.

Comment 3 Sandro Bonazzola 2016-05-02 10:10:43 UTC
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Comment 4 Yaniv Lavi 2016-05-23 13:26:30 UTC
oVirt 4.0 beta has been released, moving to RC milestone.

Comment 5 Yaniv Lavi 2016-05-23 13:26:52 UTC
oVirt 4.0 beta has been released, moving to RC milestone.

Comment 6 Yevgeny Zaspitsky 2016-06-15 15:50:41 UTC
In my offline discussion with Sharon was agreed:

* The problem is about being able to un-check a network role in the flow of Network->Clusters->Manage Networks. The engine doesn't allow dismissing a network form a role it bears without appointing another network for the role. Currently the engine doesn't perform the problematic operation, but it also doesn't report it correctly.

* As soon as this flow deals with a single network and appointing another network is impossible here, the desired solution would be disabling un-checking a role checkbox if that was checked (a network bears a role) on the dialog start. Also we might consider adding a description (tooltip) describing why the checkbox is disabled.

Yaniv(s), please reconsider the bug priority/targeting according to this description.

Comment 7 Yevgeny Zaspitsky 2016-06-16 03:36:14 UTC
Dan, same request for you, as you are the first one who set the target.

Comment 8 Michael Burman 2017-02-19 14:56:06 UTC
Verified on - 4.1.1.2-0.1.el7


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