Schema transformer was incorrecty using si_name to delete VM object. It should
use vm_name. Because of this, stale VM objects remain in schema transformer
local memory and so, if SI is created again, it thinks the VM exists but no VMIs
exist and hence service chain is not created.
This is partial fix because we still do not break service chain when SI is deleted.
Change-Id: I4458352e3af0feeb1f68c57920b6875991cfac81
Partial-Bug: 1499125
(cherry picked from commit b5fe2fa3a6a2648e3e7a8d0759cd53dfce9ada93)
Reviewed: https:/ /review. opencontrail. org/14213 github. org/Juniper/ contrail- controller/ commit/ 5558248eff5c014 d6949365ffe4091 331b25760b
Committed: http://
Submitter: Zuul
Branch: R2.20.x
commit 5558248eff5c014 d6949365ffe4091 331b25760b
Author: Sachin Bansal <email address hidden>
Date: Wed Sep 23 19:58:10 2015 -0700
Use vm_name to delete the VM object
Schema transformer was incorrecty using si_name to delete VM object. It should
use vm_name. Because of this, stale VM objects remain in schema transformer
local memory and so, if SI is created again, it thinks the VM exists but no VMIs
exist and hence service chain is not created.
This is partial fix because we still do not break service chain when SI is deleted.
Change-Id: I4458352e3af0fe eb1f68c57920b68 75991cfac81 e3e7a8d0759cd53 dfce9ada93)
Partial-Bug: 1499125
(cherry picked from commit b5fe2fa3a6a2648