| 2021-11-12 13:05:28 |
Hiromu Asahina |
description |
After creating VNF Instance using vnflcm v1 API, tacerk-horizon VNF Manager tab becomes not being able to redner the view correctly.
1. Create a VNF Instance according to [1]
2. Access VNF Manager tab in tacker-horizon
3. An error message `Error: Unable to get instances 'vim_name'` appears and any VNFs created aren't displayed.
The cause of this problem is the contents of `placement_attr` that the horizon uses to get `vim_name` have changed in v1 API.
Thus, we have to use `get` method to handle a case where `vim_name` isn't available in `placement_attr`.
[1] https://docs.openstack.org/tacker/latest/user/etsi_vnf_deployment_as_vm_with_user_data.html
[2] https://opendev.org/openstack/tacker-horizon/src/branch/master/tacker_horizon/openstack_dashboard/dashboards/nfv/vnfmanager/tabs.py#L56 |
After creating VNF Instance using vnflcm v1 API, tacker-horizon VNF Manager tab becomes not being able to redner the view correctly.
1. Create a VNF Instance according to [1]
2. Access VNF Manager tab in tacker-horizon
3. An error message `Error: Unable to get instances 'vim_name'` appears and any VNFs created aren't displayed.
The cause of this problem is the contents of `placement_attr` that the horizon uses to get `vim_name` have changed in v1 API.
Thus, we have to use `get` method to handle a case where `vim_name` isn't available in `placement_attr`.
[1] https://docs.openstack.org/tacker/latest/user/etsi_vnf_deployment_as_vm_with_user_data.html
[2] https://opendev.org/openstack/tacker-horizon/src/branch/master/tacker_horizon/openstack_dashboard/dashboards/nfv/vnfmanager/tabs.py#L56 |
|
