| Summary: | [webadmin] GUI is lacking the check connectivity option for HOST's mgmt networks | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | zvi <zfridler> | ||||
| Component: | ovirt-engine-webadmin | Assignee: | Danny Rankevich <drankevi> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | unspecified | CC: | acathrow, ecohen, iheim, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-02-29 13:28:50 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
zvi
2012-01-18 10:40:28 UTC
The problem is not the lack of "check connectivity"; the problem is that the management network isn't recognized in the GUI as the management network, and it is treated wrongfully as a regular network
If it had been recognized as the management network, its name should have been marked in bold, with asterisk ("*") next to it, and when selected - the "Edit Management Network" button should be enabled - not the "Add / Edit" button.
I am not sure if the bug is a GUI bug or a backend (engine-core) bug: The backend should report regarding each NIC if it is the management NIC or not (VdsNetworkInterface.getIsManagement()). So either the backend doesn't report this property appropriately, or the GUI doesn't read it appropriately.
In any case, this should be taken care of as part of in the new setup-network GUI.
Created attachment 556006 [details]
mgmt network - correct view vs. incorrect view
It looks like this was done on a network which is not the management network. If anyone has a scenario in which this behavior can be reproduced, please re-open the BZ with exact steps to reproduce. |