Until this gets fixed, all nova changes will fail.
Based on the timing of when it started showing up, this was probably triggered by a change in the base image that nodepool created, possibly a libvirt upgrade? Unfortunately for unit tests we don't dump the package list, which would make that easier to debug.
This is a 100% failure at this point in the gate, categorized by - http:// logstash. openstack. org/#eyJzZWFyY2 giOiJtZXNzYWdlO lwiQXR0cmlidXRl RXJyb3I6IHZpckN vbm5lY3QgaW5zdG FuY2UgaGFzIG5vI GF0dHJpYnV0ZSAn cmVnaXN0ZXJDbG9 zZUNhbGxiYWNrJ1 wiIiwiZmllbGRzI jpbXSwib2Zmc2V0 IjowLCJ0aW1lZnJ hbWUiOiIxNzI4MD AiLCJncmFwaG1vZ GUiOiJjb3VudCIs InRpbWUiOnsidXN lcl9pbnRlcnZhbC I6MH0sInN0YW1wI joxMzg5MDg0ODQw ODAyfQ= =
Until this gets fixed, all nova changes will fail.
Based on the timing of when it started showing up, this was probably triggered by a change in the base image that nodepool created, possibly a libvirt upgrade? Unfortunately for unit tests we don't dump the package list, which would make that easier to debug.