db_resync_done lock is used to indicate the amqp thread to wait for resync to
complete. In this case, when we call SchemaTransformer.destroy_instance()
due to Casandra connection failure, this lock remains locked blocking
destroy_instance. destroy_instance calls _vnc_subscribe_callback to drain the
amqp queue which waits infinitely for db_resync_done lock to be released.
This fix releases db_resync_done lock so that destroy_instance doesnt get
blocked.
Reviewed: https:/ /review. opencontrail. org/47491 github. com/Juniper/ contrail- controller/ commit/ 6a29730679db237 5c0eee7006de266 5b53cf979d
Committed: http://
Submitter: Zuul v3 CI (<email address hidden>)
Branch: master
commit 6a29730679db237 5c0eee7006de266 5b53cf979d
Author: Shivayogi Ugaji <email address hidden>
Date: Mon Nov 5 22:07:18 2018 -0800
db_resync_done lock is used to indicate the amqp thread to wait for resync to er.destroy_ instance( ) callback to drain the
complete. In this case, when we call SchemaTransform
due to Casandra connection failure, this lock remains locked blocking
destroy_instance. destroy_instance calls _vnc_subscribe_
amqp queue which waits infinitely for db_resync_done lock to be released.
This fix releases db_resync_done lock so that destroy_instance doesnt get
blocked.
Change-Id: Ic81fd0acda0fd4 d43b3bfd061b475 27b150b9096
Closes-Bug: #1801474