libvirt calls aren't reliably using tpool.Proxy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
Undecided
|
Matthew Booth |
Bug Description
A customer is hitting an issue with symptoms identical to bug 1045152 (from 2012). Specifically, we are frequently seeing the compute host being marked down. From log correlation, we can see that when this occurs the relevant compute is always in the middle of executing LibvirtDriver.
Because eventlet, we proxy libvirt calls at the point we create the libvirt connection in libvirt.
return tpool.proxy_call(
This means: run libvirt.
There are 2 problems with this. Firstly, the autowrap list is incomplete. At the very least we need to add libvirt.
Secondly, and the specific root cause of this bug, it doesn't understand lists:
In LibvirtDriver.
tags: | added: libvirt |
Fix proposed to branch: master /review. opendev. org/677736
Review: https:/