After creating VNF Instance using vnflcm v1 API, tacker-horizon VNF
Manager tab becomes not being able to redner the view correctly. This
happens because VNF Manager tab tries to obtain `vim_name` and fails.
The `vim_name` attribute is no longer available in vnflcm v1 API.
This patch fix this problem by simply using `get` method to obtain
`vim_name`.
Reviewed: https:/ /review. opendev. org/c/openstack /tacker- horizon/ +/817876 /opendev. org/openstack/ tacker- horizon/ commit/ 1d18379c944fceb 56c6367b50c1734 e037eee486
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 1d18379c944fceb 56c6367b50c1734 e037eee486
Author: Hiromu Asahina <email address hidden>
Date: Fri Nov 12 22:03:15 2021 +0900
Fix rendering failure in the VNF Manager tab
After creating VNF Instance using vnflcm v1 API, tacker-horizon VNF
Manager tab becomes not being able to redner the view correctly. This
happens because VNF Manager tab tries to obtain `vim_name` and fails.
The `vim_name` attribute is no longer available in vnflcm v1 API.
This patch fix this problem by simply using `get` method to obtain
`vim_name`.
Closes-bug: #1950783 4cde5678a07df9f 55382eb5481
Signed-off-by: Hiromu Asahina <email address hidden>
Change-Id: If78ffe41dbe3e0