Clearing service instance DB State after STOP command
If Delete of service instance is received before it was marked
unusable, StopServiceInstance command is issued, which invokes
the namespace script. And immediately after this, DB state is cleared.
Clearing of DB State can result in deleting of service instance
DBEntry before namespace script completion. SIGCHILD event after
script completion looks for service instance that triggered the
task, and results in crash as the service isntance is already deleted.
To avoid crash, the DBState is cleared after processing the SIGCHILD
event.
Reviewed: https:/ /review. opencontrail. org/10887 github. org/Juniper/ contrail- controller/ commit/ 080dda0c6af5eb1 72e7690854326ba 230d349388
Committed: http://
Submitter: Zuul
Branch: master
commit 080dda0c6af5eb1 72e7690854326ba 230d349388
Author: Divakar <email address hidden>
Date: Tue May 26 21:40:44 2015 -0700
Clearing service instance DB State after STOP command
If Delete of service instance is received before it was marked
unusable, StopServiceInstance command is issued, which invokes
the namespace script. And immediately after this, DB state is cleared.
Clearing of DB State can result in deleting of service instance
DBEntry before namespace script completion. SIGCHILD event after
script completion looks for service instance that triggered the
task, and results in crash as the service isntance is already deleted.
To avoid crash, the DBState is cleared after processing the SIGCHILD
event.
Testcases to follow in the next commit
Change-Id: I212063ede8f7df 4b693771aa394c4 536a76d8d20
closes-bug: #1453956