Problem:
When all the VMI's are gone multicast object is deleted. However VN is still not
gone and meanwhile new VMI gets added. During this window where all VMI were
gone to new VMI gets added, olist for replication tree is received from
control-node. This update is neglected in absence of multicast object for same.
This results in no multicast tree.
Solution:
Retain multicast object till two conditions are met:
- All VMIS are gone
- VN is no more in use by multicast.
Reviewed: https:/ /review. opencontrail. org/16313 github. org/Juniper/ contrail- controller/ commit/ d58bf7f94d007f5 5807d26d09d4fba e50066d5ac
Committed: http://
Submitter: Zuul
Branch: master
commit d58bf7f94d007f5 5807d26d09d4fba e50066d5ac
Author: Manish <email address hidden>
Date: Fri Jan 15 08:56:00 2016 +0530
Multicast traffic gets dropped.
Problem:
When all the VMI's are gone multicast object is deleted. However VN is still not
gone and meanwhile new VMI gets added. During this window where all VMI were
gone to new VMI gets added, olist for replication tree is received from
control-node. This update is neglected in absence of multicast object for same.
This results in no multicast tree.
Solution:
Retain multicast object till two conditions are met:
- All VMIS are gone
- VN is no more in use by multicast.
Change-Id: Ica43ce9ed4951f 644d9049b354e07 64c860ef4d4
Closes-bug: 1529829