CNF Deployment failed due to missing Default VIM

[Ashutosh Mishra]

While creating VNF I got the error -

[stack@instance-vnfm-centos8-stream-20210730 test]$ openstack vnflcm create 1c2add2d-e6ed-4858-981b-a30e89857524
Default VIM is not defined.

This is because, in the "ETSI NFV-SOL CNF Deployment" document the kubernetes VIM created is not default.

We need to make the kubernetes VIM as default VIM.

Document Followed:
https://docs.openstack.org/tacker/latest/user/etsi_containerized_vnf_usage_guide.html#register-kubernetes-vim

[OpenStack Infra (hudson-openstack)]

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

[Masaki UENO (masaki-ueno)]

Thank you for your report and contribution.

I got this problem in my environment, and I've also noticed that this problem can be resolved even if the target k8s VIM is not default.

In the current implementation, at least 1 default VIM is needed for invoking `Create VNF Request` (i.e. `openstack vnflcm create`), thus if other VIM such as Openstack VIM is specified as default, your problem is not occurred.

I will review your proposal patch later, thank you.

[Ashutosh Mishra (ashutosh15)]

Thank You Masaki San for your Response.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/tacker/+/837499
Committed: https://opendev.org/openstack/tacker/commit/594fffcc0e17e3c579f33858846ae61d2eed71f5
Submitter: "Zuul (22348)"
Branch: master

commit 594fffcc0e17e3c579f33858846ae61d2eed71f5
Author: Ashutosh Mishra <email address hidden>
Date: Tue Apr 12 08:10:11 2022 +0000

    CNF Deployment failed due to missing Default VIM

    This patch makes kubernetes VIM as Default VIM,
    in "ETSI NFV-SOL CNF Deployment" Documentation.

    Closes-Bug: 1968680
    Change-Id: I8a9e763a0ef7df07135ebfbdcc9fa104b778ee77

[OpenStack Infra (hudson-openstack)]

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