Bug 1073624
| Summary: | Nova delete fails due to Libvirtd timeout | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Joe Talerico <jtaleric> |
| Component: | openstack-nova | Assignee: | Daniel Berrangé <berrange> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Ami Jeain <ajeain> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | CC: | areis, chaochin, dmaley, ebarrera, jdenemar, knoel, kwolf, ndipanov, pbonzini, sclewis, sgordon, stefanha, yeylon |
| Target Milestone: | --- | Keywords: | Reopened, ZStream |
| Target Release: | 4.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-30 15:45:34 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: | 1040649, 1081488 | ||
|
Description
Joe Talerico
2014-03-06 20:10:38 UTC
This doesn't look like a bug in qemu-kvm. It rather looks like the host is so busy processes don't die early enough even after SIGKILL. I guess deleting a guest in nova means the guest is destroyed and undefining it. It seems to me that nova calls virDomainDestroyFlags() and since it fails (due to the timeout), it doesn't do the rest. And once the qemu-kvm process actually dies, nova reports the guest as ShutOff. A possible solution could be to move the rest of the deletion process to a VIR_DOMAIN_EVENT_STOPPED handler, which would make sure the domain is deleted once it stops. Another option would be to introduce new flag for virDomainDestroyFlags to make it wait until the process dies instead of giving up after 15 seconds. Dan, can you take a look at this and see if nova's libvirt driver should be changed per Jiri's comment #4? Seems Nova could just retry the destroy operation, and/or undefine the guest regardless. By email we discussed whether or not this was still an issue with a newer version of Nova. I don't think I heard back on that. If it is, I think this is something that should just be tracked upstream. Please report a bug on launchpad if you're able to reproduce. Thanks! Eduard, we haven't received any further information from you about the customer's issue in response to Dan's comment. As a result I am closing this bug. A bug is opened in OpenStack community --> https://bugs.launchpad.net/nova/+bug/1387950 |