commit 03b3fe6f981ff130e08c15c0a0cf92d7d71f5c10
Author: Ken Fujimoto <email address hidden>
Date: Fri Feb 9 08:05:03 2024 +0000
Fix kubernetes resource existence check in v2 API
This patch fixes the problem that instantiating a vnf instance
succeeds wrongly when a resource made by another instance with
the same name exists.
This patch adds "tacker_vnf_instance_id" to metadata.labels
when creating kubernetes resources in CNF v2 API Instantiate,
and when creating or deleting resources, if the resource already
exists, it checks if it was created in own vnf instance by
metadata.labels.
Reviewed: https:/ /review. opendev. org/c/openstack /tacker/ +/909063 /opendev. org/openstack/ tacker/ commit/ 03b3fe6f981ff13 0e08c15c0a0cf92 d7d71f5c10
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 03b3fe6f981ff13 0e08c15c0a0cf92 d7d71f5c10
Author: Ken Fujimoto <email address hidden>
Date: Fri Feb 9 08:05:03 2024 +0000
Fix kubernetes resource existence check in v2 API
This patch fixes the problem that instantiating a vnf instance vnf_instance_ id" to metadata.labels labels.
succeeds wrongly when a resource made by another instance with
the same name exists.
This patch adds "tacker_
when creating kubernetes resources in CNF v2 API Instantiate,
and when creating or deleting resources, if the resource already
exists, it checks if it was created in own vnf instance by
metadata.
Closes-Bug: #2053098 f9689d89d24c1db 28de8e2dc90
Change-Id: I4a22fc50706750