Bug 1071988
| Summary: | Fatal error during migration within engine logs. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Nikolai Sednev <nsednev> | ||||
| Component: | ovirt-engine-core | Assignee: | bugs <bugs> | ||||
| Status: | CLOSED CANTFIX | QA Contact: | Pavel Stehlik <pstehlik> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.4 | CC: | acathrow, amureini, gklein, iheim, michal.skrivanek, nsednev, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.4.1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | virt | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-04-07 14:08:15 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: |
|
||||||
This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1. This bug is about VM migration, not storage migration "5.Expect for fatal error on engine, within it's logs." so you're looking at logs or are you concerned about the even log in UI? (In reply to Michal Skrivanek from comment #3) > "5.Expect for fatal error on engine, within it's logs." > > so you're looking at logs or are you concerned about the even log in UI? I'm concerned about not informative error within WEBUI and the log "fatal error", which should not happen at all, if happens, should be precise. Actual results: Fatal error happens, which is not informative and should be because of connectivity issue, as host b is unreachable. Expected results: Host b is unreachable, hence migration failed. we can't reliably show much more details. We've discussed that before that it's not really doable, there are too many components where things go wrong. Moreover I'm not sure you attached the right logs, I see few migrations, succeeding. OK, If you think it's OK, then I don't have nothing to add on this. If "fatal error" is OK with the customer... I'm not sure. The logs provided received during described scenario flow, if something is missing, please assign on storage team for reproduction. it's just that we can't provide anything better... |
Created attachment 870009 [details] engine and vdsm logs. Description of problem: Fatal error during migration within engine logs. Version-Release number of selected component (if applicable): ovirt-engine-3.4.0-0.7.beta2.el6.noarch qemu-kvm-rhev-0.12.1.2-2.415.el6_5.4.x86_64 libvirt-0.10.2-29.el6_5.3.x86_64 sanlock-2.8-1.el6.x86_64 How reproducible: Always Steps to Reproduce: 1.Assemble cluster of two hosts and one up and running VM. 2.Start live VM migration from host a to host b. 3.During migration of host a to b, while process still running, cut off the host b using iptables on host a, so host b will become unreachable. 4.Disable and enable several times iptables rule defined on host a. 5.Expect for fatal error on engine, within it's logs. Actual results: Fatal error happens, which is not informative and should be because of connectivity issue, as host b is unreachable. Expected results: Host b is unreachable, hence migration failed. Additional info: engine, vdsm logs. Please check time in log around 2014-03-03 17:24:46.