Bug 1124808
| Summary: | [webadmin] bond gets visually broken if its slave is ifdowned | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Martin Pavlik <mpavlik> | ||||||||||
| Component: | ovirt-engine-webadmin | Assignee: | Lior Vernia <lvernia> | ||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Martin Pavlik <mpavlik> | ||||||||||
| Severity: | urgent | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 3.5 | CC: | acathrow, bazulay, danken, ecohen, gklein, iheim, mgoldboi, yeylon | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | network | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2014-07-31 12:18:59 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 922503 [details]
screnshot: before ifdown
Created attachment 922504 [details]
screnshot: after ifdown
Created attachment 922505 [details]
vdsClient outputs before and after ifdown
if both interfaces are ifdowned, bond in GUI (netowrk subtab and setup networks dialog) just disappears completely that is very confusing for user (it appears like bond is not configured at all) I think that it appears like the bond is not configured at all because it isn't configured at all. If you ifdown both interfaces, then they're disconnected from the bond, and oVirt doesn't display bonds that aren't connected to any interface. If you want to simulate a case where there's some malfunction, use "ip link set <DEV_NAME> down". Dan, correct me if I'm wrong. Well, an interface can be down, but still connected to a bond device. However, the ifdown script explicitly takes it out of the bond. I think that it would be cool if Engine could handle a bond with no slaves (it should be considered non-functional, of course). In any case, this bug is not urgent: if someone logs into his hypervisor and messes his network, we show that the network is messed up. Any complimentary information is welcome, but not urgently needed. |
Created attachment 922502 [details] log_collector Description of problem: if one of host bond slave interfaces is manually shutdown using ifdown command and refresh host capabilities button is used afterwards, the slave which was shut down is removed from bond in Host -> Network interfaces sub-tab Version-Release number of selected component (if applicable): oVirt Engine Version: 3.5.0-0.0.master.20140722232056.git8e1babc.fc19 How reproducible: 100% Steps to Reproduce: 1.create bonded interface at host (via Setup Networks) 2.ssh to host and use ifdown command to shut down one of the bond slave interfaces (e.g. ifdown p1p1) 3.hit "Refresh Capabilities" button in webadmin Actual results: slave interface which went down is removed from the bond Expected results: slave interface remains in bond and is marked as down Additional info: - interface is returned to the bond after ifup is used on it - vdsClient before and after ifdown are attached