Description of problem: running a stack delete while instances are busy sometimes results in errors: 2018-02-14 20:27:59.748 1 ERROR oslo_messaging.rpc.server libvirtError: internal error: unable to execute QEMU command 'device_del': Device 'virtio-disk2' not found and failure to detach the volumes, resulting stack delete failure. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create stack 2. Create load 3. Delete stack Actual results: Volumes showing as DELETE_FAILED Expected results: Volumes get deleted. Additional info: We've tried raising the following to compensate: - haproxy server and client timeout to 5 minutes - cinder workers to 56 (to match number of cpus) - keystone rpc timeout to 300s - cinder rpc timeout to 300s
What volume driver is being used here?
As per the sosreports: etc/cinder/cinder.conf:volume_driver=cinder.volume.drivers.dell_emc.vnx.driver.VNXDriver
Lee, can someone from the Nova team take a look at the nova error? Cinder team is not sure whether this bug is Cinder or Nova related. It is not possible to duplicate without a VNX array.
(In reply to Thiago da Silva from comment #5) > Lee, can someone from the Nova team take a look at the nova error? Cinder > team is not sure whether this bug is Cinder or Nova related. It is not > possible to duplicate without a VNX array. Moving this across to Nova, this looks like guest is still sending I/O to the volume, we've recently started ignoring this upstream and it should be a trivial backport downstream into OSP 12. [1] https://review.openstack.org/#/c/546423/ [2] https://bugs.launchpad.net/nova/+bug/1750680
*** This bug has been marked as a duplicate of bug 1551733 ***