Bug 1641617
Summary: | [Executor] Worker blocked vdsm error happens while HE VM migration.Followed by unreachable SDs | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Polina <pagranat> | ||||||||
Component: | BLL.Virt | Assignee: | Ryan Barry <rbarry> | ||||||||
Status: | CLOSED WORKSFORME | QA Contact: | Polina <pagranat> | ||||||||
Severity: | urgent | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 4.2.7 | CC: | bugs, lrotenbe, michal.skrivanek, pagranat, rbarry, stirabos | ||||||||
Target Milestone: | ovirt-4.4.0 | Keywords: | Automation, AutomationBlocker, TestOnly | ||||||||
Target Release: | --- | Flags: | pm-rhel:
ovirt-4.4+
|
||||||||
Hardware: | x86_64 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2019-09-16 19:09:41 UTC | Type: | Bug | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Polina
2018-10-22 11:13:08 UTC
Created attachment 1501681 [details]
he migration error logs
We hit the migration error in high frequency, this time in:
ovirt-engine-4.2.7.4-0.1.el7ev.noarch
It's strongly effect our automation.
Re-targeting, because these bugs either do not have blocker+, or do not have a patch posted Polina, still reproducible? Created attachment 1527555 [details]
migration_last_4.2.8-5_build.tar.gz
yes, I see it in the last automation run
I attach migration_last_4.2.8-5_build.tar.gz - containing the extracted of engine and the vdsm logs with the errors around the incident time .
Please let me know if more logs needed.
I do not see any problem with SD? Is there anything in event log? Removing blocker+ until there's a reproducer in engineering. Can you please attach libvirt/qemu logs, so we can get an idea why the VM doesn't start? Simone, any idea why the host is allowed to go into maintenance when the HE VM is actually still running there, and potential side effects other than the observed storage disconnect? it can definitely happen when host becomes unresponsive during PreparingForMaintenance (see MaintenanceVdsCommand) Polina, so what is the problem again? Re-test? will be re-tested in the next automation run . not seen in the last automation runs (all the tiers) for ovirt-engine-4.3.6.5-0.1.el7.noarch |