[K8s]: Project deletion non handled correctly after multi cluster changes
Bug #1779620 reported by
Pulkit Tandon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R5.0 |
Fix Released
|
High
|
Dinesh Bakiaraj | |||
Trunk |
Fix Released
|
High
|
Dinesh Bakiaraj |
Bug Description
R5.0-117
After deletion of namespace, corresponding project is not getting deleted from contrail.
This has happened after multi cluster changes have been introduced.
While doing a rough inspcetion, following piece of code might be buggy:
File:
/usr/lib/
Lines:
554 # delete the namespace
555 self._delete_
which further calls:
NamespaceKM.
I think it will return None if you use ns_name without cluster name appended.
Thus, deletion will fail.
I could be wrong here.
To post a comment you must log in.
The namespace delete problem is here:
https:/ /github. com/Juniper/ contrail- controller/ blob/master/ src/container/ kube-manager/ kube_manager/ vnc/vnc_ namespace. py#L563 config. cluster_ project_ name(name) == project.name:
The check should be : if vnc_kube_