Improper status when create a resource with the same name in v2 API

[Kenta Fukaya]

Improper status when create a resource with the same name in v2 API.
There is a bug that allows a single resource to be operated from multiple VNF instances.

This bug is caused by the fact that when Instantiate is executed,
it exits successfully even if there is already a resource with the same namaespace/kind/metada.name.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/tacker/+/909063

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/tacker/+/909063
Committed: https://opendev.org/openstack/tacker/commit/03b3fe6f981ff130e08c15c0a0cf92d7d71f5c10
Submitter: "Zuul (22348)"
Branch: master

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.

    Closes-Bug: #2053098
    Change-Id: I4a22fc50706750f9689d89d24c1db28de8e2dc90

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tacker 11.0.0.0rc1 release candidate.