Bug 1749382
| Summary: | Leftover Libvirt VMs on Compute nodes | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | kforde | |
| Component: | openstack-nova | Assignee: | melanie witt <mwitt> | |
| Status: | CLOSED ERRATA | QA Contact: | OSP DFG:Compute <osp-dfg-compute> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 13.0 (Queens) | CC: | dasmith, jhakimra, kchamart, lyarwood, mbooth, mwitt, sbauza, sclewis, sgordon, stephenfin, vromanso | |
| Target Milestone: | Upstream M3 | Keywords: | Triaged | |
| Target Release: | 16.0 (Train on RHEL 8.1) | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-nova-20.0.1-0.20191025043858.390db63.el8ost | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1753453 1753455 1763329 (view as bug list) | Environment: | ||
| Last Closed: | 2020-02-06 14:42:04 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: | 1753453, 1753455, 1763329 | |||
|
Description
kforde
2019-09-05 13:49:51 UTC
Just wanted to note that the fix for this bug is going to be a workaround via the --before feature: nova-manage archive_deleted_rows --before <date> This way, when running a cron to archive_deleted_rows, a --before <date> can be used to ensure that very recently deleted instances will *not* be archived at an inopportune time, for example, when the cluster is down/experiencing an outage. Then, when the cluster is restored, the normal periodic reap task will take care of cleaning up the orphaned deleted instance's libvirt guests. Besides this workaround, there is a patch in-flight upstream to fix the root cause by cleaning up libvirt guests that are "unknown" to nova: https://review.opendev.org/627765 but it is very complicated and is not close to a mergeable state yet. There are dangers (race conditions) around potentially destroying libvirt guests that are not orphans for instances that are in the middle of migrating. Change was merged upstream in Train before the M1 milestone. (In reply to melanie witt from comment #5) > Change was merged upstream in Train before the M1 milestone. https://review.opendev.org/556751 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:0283 |