[R4.1 Build 7]: VM object deletion takes 3 minutes after k8s POD deletion
Bug #1735652 reported by
Pulkit Tandon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R4.1 |
Fix Released
|
High
|
Hari Prasad Killi | |||
Trunk |
Fix Released
|
High
|
Hari Prasad Killi |
Bug Description
R4.1 - Build 7
HA K8s setup with control data interfaces provisioned.
3 controllers and 2 computes
1 Kube master and 2 Slaves
Description:
Many sanity test cases failed on a check where we verify that after deletion of a Pod, corresponding VM object gets deleted from the agent.
Observed that in random cases, the VM object does not get deleted.
After running manually, found that agent removes the VM info after 3 minutes.
Thus, test case failed.
Logs can be found in following sanity run:
http://
CNI logs attached
information type: | Proprietary → Public |
no longer affects: | juniperopenstack/r4.0 |
tags: | added: sanityblocker |
To post a comment you must log in.
This scenario has ECMP. When one VM is deleted, the flows continue as there are other VMs but the flow entry is still holding a reference to the deleted VM. Because of this the VM object is not freed till the flow gets deleted.