>> The communication with cinder is async, Nova doesn't wait or check if >> the detach on cinder side has been executed correctly. > > Yeah, I guess nova gets the 202 back: > > http://logs.openstack.org/18/258118/2/check/gate-tempest-dsvm-full-ceph/7a5290d/logs/screen-n-cpu.txt.gz#_2015-12-16_03_30_43_990 > > > Should nova be waiting for detach to complete before it tries deleting > the volume (in the case that delete_on_termination=True in the bdm)? > > Should nova be waiting (regardless of volume delete) for the volume > detach to complete - or timeout and fail the instance delete if it doesn't?
I'll revisit this change next year trying to look at the problem in a different way. Thank you all for your time and all the suggestions. -- Andrea Rosa __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev