Bug 849163
| Summary: | [RHEVM] [backend] [TEXT] rhevm reports missing <UNKNOWN> network after required bond on host goes down | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Martin Pavlik <mpavlik> | ||||||
| Component: | ovirt-engine | Assignee: | Muli Salem <msalem> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Pavlik <mpavlik> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 3.1.0 | CC: | dyasny, gklein, iheim, lpeer, mkenneth, Rhev-m-bugs, yeylon, ykaul | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | network | ||||||||
| Fixed In Version: | si16 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-12-04 20:00:53 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 605202 [details]
screenshot
Proble appears for DC/CL 3.0 as well as for DC/CL 3.1 Proposed patch in: http://gerrit.ovirt.org/#/c/7424/ |
Created attachment 605201 [details] vdsm.log + engine.log Description of problem: If there is a required network connected to host over a bond, and the bond goes down, following error appears in events Host dell-r210ii-08.rhev.lab.eng.brq.redhat.com moved to Non-Operational state because interfaces 'p1p1, p1p2' are down which needed by networks '<UNKNOWN>' in the current cluster Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization Manager Version: '3.1.0-12.el6ev' libvirt-0.9.10-21.el6_3.3.x86_64 qemu-img-rhev-0.12.1.2-2.295.el6.x86_64 vdsm-4.9-113.1.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Create required logical network 2. Attach the network to host over bond 3. ssh to host and shut all bond interfaces down 4. wait for a few minutes, host will go non operational and error message will appear (see screenshot) Actual results: '<UNKNOWN>' network is reported to be the problem Expected results: The error message should contain a correct network name Additional info: Corresponding message from engine log: 2012-08-17 15:40:36,796 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (QuartzScheduler_Worker-55) [5a0d3b6] Host 'dell-r210ii-08.rhev.lab.eng.brq.redhat.com' moved to Non-Operational state because interface/s 'p1p1, p1p2, ' are down which needed by network/s '' in the current cluster