| Summary: | UI: explain why we cannot change the logical network settings in the "Manage Networks" window | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Sharon Gratch <sgratch> | ||||
| Component: | BLL.Network | Assignee: | Yevgeny Zaspitsky <yzaspits> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Meni Yakove <myakove> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 4.0.0 | CC: | bugs, danken, mburman, ylavi | ||||
| Target Milestone: | ovirt-4.1.1 | Keywords: | Reopened | ||||
| Target Release: | 4.1.1.2 | Flags: | rule-engine:
ovirt-4.1+
|
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-04-21 09:53:40 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: | |||||
| Attachments: |
|
||||||
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. 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. Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA. oVirt 4.0 beta has been released, moving to RC milestone. oVirt 4.0 beta has been released, moving to RC milestone. 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. Dan, same request for you, as you are the first one who set the target. Verified on - 4.1.1.2-0.1.el7 |
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