Bug 844344
Summary: | [engine-core] null pointer exception due to unhandled migration failure (Failed to create ExecutionContext for MigrateVmCommand: java.lang.NullPointerException) | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Haim <hateya> |
Component: | ovirt-engine | Assignee: | Eli Mesika <emesika> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Barak Dagan <bdagan> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.1.0 | CC: | abaron, dyasny, emesika, iheim, lpeer, michal.skrivanek, oramraz, pstehlik, Rhev-m-bugs, sgrinber, yeylon, ykaul |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | virt | ||
Fixed In Version: | si18 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-05-09 15:14:58 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: | |||
Bug Depends On: | |||
Bug Blocks: | 818289, 870745 |
Description
Haim
2012-07-30 11:19:50 UTC
Please add exact steps of how to reproduce and additional info (how many hosts in cluster, is that host also the SPM etc.) After talking to Eli... seems to me quite unlikely to happen. Can you confirm this is a consequence of blocking/failing the vdsm connectStoragePool? If so this won't likely happen at customer site unless things are broken/misconfigured and hence the priority is low and I would suggest rhevm_future. reolved as a result of fixing BZ 818289 http://gerrit.ovirt.org/#/c/7494/ (In reply to comment #3) > After talking to Eli... > > seems to me quite unlikely to happen. > Can you confirm this is a consequence of blocking/failing the vdsm > connectStoragePool? > If so this won't likely happen at customer site unless things are > broken/misconfigured and hence the priority is low and I would suggest > rhevm_future. Actually it's quite easy to reproduce this scenario: https://bugzilla.redhat.com/show_bug.cgi?id=732479 Failure to connect to pool means that host should not be up. When sending a connectStoragePool command when already connected to *this* pool the command will succeed, not fail. It will only fail if: 1. there was a problem when trying to connect 2. vdsm is already connected to a different pool. The patch above does not deal with the underlying issue (host should be moved to up only if it successfully connected to pool and getVdsStats reported that everything is ok). |