Bug 1079964
| Summary: | Non operational host- audit log doesn't contain bond's name if there is also problematic nic | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Alona Kaplan <alkaplan> | ||||||
| Component: | ovirt-engine-core | Assignee: | Alona Kaplan <alkaplan> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 3.5 | CC: | bugs, gklein, iheim, masayag, rbalakri, yeylon | ||||||
| Target Milestone: | --- | Keywords: | Triaged | ||||||
| Target Release: | 3.5.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | network | ||||||||
| Fixed In Version: | ovirt-3.5.0-alpha2 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-10-17 12:20:11 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: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 878382 [details]
Audit log doesn't contain all networks on bond
Another bug in the same area- if there is more than one network on the same bond (non vm + vlan or vlan + vlan) and the bond is down- the audit log message contains just one of the networks on the bond and not all of them. One more bug- if the network is over vlan and the interface is down- the audit log contains the interface.vlan name and not the parent interface name as expected. Actual result: Host grey-vdsh moved to Non-Operational state because interfaces 'eth3.444' are down but are needed by networks 'vlan444' in the current cluster Expected result: Host grey-vdsh moved to Non-Operational state because interfaces 'eth3' are down but are needed by networks 'vlan444' in the current cluster When the engine checks if the host has to move to non-operational state it determines the status of a bond according to the status of its slaves (if any of the slaves is up the bond is up, otherwise down). Vdsm started reporting bonding state back in rhev-3.0 commit bf27268b4d1a9b07dea63f9fcd1f1d8842fe082a Therefore, the old Engine calculation should be scrapped, and the engine should depend on Vdsm's reports. This is an automated message. oVirt 3.4.1 has been released. This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed. verified on ovirt-engine-3.5.0-0.0.master.20140605145557.git3ddd2de.el6.noarch oVirt 3.5 has been released and should include the fix for this issue. |
Created attachment 878026 [details] Audit log doesn't contain bond's name Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create required network- 'net1' 2. Create required networks- 'net2' 3. Open setup networks 4. Create bond1 between eth1 and eth2 5. Attach net1 to bond1 6. Attach bond2 to eth2 7. Try to activate the host 8. The activation fails and the host moves to non-operational state and an audit log is reported. Actual results: The audit log is- Host grey-vdsh moved to Non-Operational state because interfaces 'eth3' are down but are needed by networks 'net1, net2' in the current cluster Expected results: Host grey-vdsh moved to Non-Operational state because interfaces 'eth1, eth2, eth3' are down but are needed by networks 'net1, net2' in the current cluster or Host grey-vdsh moved to Non-Operational state because interfaces 'bond1, eth3' are down but are needed by networks 'net1, net2' in the current cluster Additional info: