Technical FAQ (Release THREE)

From OSM Public Wiki
Revision as of 08:39, 13 July 2017 by Garciadeblas (talk | contribs)
Jump to: navigation, search

"Instantiation failed", but VMs and networks were successfully created

Q. After trying to instantiate, I got the message that the instantiation failed without much information about the reason. After checking the logs, it seems to be a timeout issue. However, I am seeing that the VMs and networks were created at the VIM.

A. First check in the RO that there is an IP address in the management interface of each VNF of the NS. 

lxc exec RO --env OPENMANO_TENANT=osm openmano instance-scenario-list                      # to identify the running scenarios in the RO
lxc exec RO --env OPENMANO_TENANT=osm openmano instance-scenario-list <id> -vvv |grep ip   # to get verbose information on a specific scenario in the RO

If no IP address is present in the management interface of each VNF, then you are hitting a SO-RO timeout issue. The reason is typically a wrong configuration of the VIM. The way how management IP addresses are assigned to the VNFs change from one VIM to another. In all the cases, the recommendation is the following:

  • Pre-provision a management network in the VIM, with DHCP enabled. You can see, for instance, the instructions in the case of Openstack (https://osm.etsi.org/wikipub/index.php/Openstack_configuration_(Release_TWO) ).
  • Then make sure that, at instantiation time, you specify a mapping between the management network in th NS and the VIM network name that you pre-provisioned at the VIM.

If the IP address is present in the management interface, then you are probably hitting a SO-VCA timeout, caused because the VNF configuration via Juju charms takes too long. To confirm, connect to VCA container and check "juju status". 

lxc exec VCA -- juju status

Then, if you see an error, you should debug the VNF charm or ask the people providing that VNF package.

"Instantiation failed" and VMs and network were not created at VIM

Q. After trying to instantiate, I got the message that the instantiation failed without much information about the reason. I connected to the VIM and checked that the VMs are networks were not created

A. You are hitting a SO-RO timeout, caused either by the lack of communication from the RO to the VIM or because the creation of VMs and networks from the RO to the VIMs takes too long.

SO connection error: not possible to contact OPENMANO-SERVER (openmanod)

Q. The NS operational data of an instantiated NS in the SO CLI shows "Connection error: not possible to contact OPENMANO-SERVER (openmanod)"

A. Please check connectivity from SO-ub to RO container. Can you ping the RO IP address (configured in SO) from SO-ub container? If not, then make sure that osm-ro service is up and running on the RO container. 

$ lxc exec RO -- bash
root@SO-ub:~# service osm-ro status
root@SO-ub:~# OPENMANO_TENANT=osm openmano datacenter-list

Deployment fails with the error message "Not possible to get_networks_list from VIM: AuthorizationFailure: Authorization Failed: The resource could not be found. (HTTPS: 404)"

Q. During instantiation, I got, the following error message: Not possible to get_networks_list from VIM: AuthorizationFailure: Authorization Failed: The resource could not be found. (HTTPS: 404)".

A. The cause is that Openstack has not been properly added to openmano with the right credentials

Go to the RO container: 

lxc exec RO bash

Install the package python-openstackclient, in case it does not exist: 

apt install -y python-openstackclient

Execute the following commands with the appropriate substitution to check that your openstack is reachable and you can do specific actions: 

openstack --os-project-name <project-name> --os-auth-url <auth-url> --os-username <auth-username> --os-password <auth-password> --debug network list 
openstack --os-project-name <project-name> --os-auth-url <auth-url> --os-username <auth-username> --os-password <auth-password> --debug host list 
openstack --os-project-name <project-name> --os-auth-url <auth-url> --os-username <auth-username> --os-password <auth-password> --debug flavor list 
openstack --os-project-name <project-name> --os-auth-url <auth-url> --os-username <auth-username> --os-password <auth-password> --debug server list 
#providing the same URL, credentials as you provide to openmano. The (--debug) will show more info so that you will see the IP/ports it try to access

This is to ensure that you have access to the openstack endpoints and that you are using the right credentials.

Case 1. If any of the previous commands do not work, then either your connectivity to Openstack endpoints is incorrect or you are not using the right parameters. Please check internally and debug until the previous commands work. Check also the guidelines here: OSM_Release_TWO#Openstack_site.

Case 2. If all of them worked, then follow these guidelines:

  • Use "v2" authorization URL. "v3" is currently experimental in the master branch and is not recommended yet.
  • If https (instead of http) is used for authorization URL, you can either use the insecure option at datacenter-create (See Openstack_configuration_(Release_TWO)#Add_openstack_at_OSM); or install the certificate at RO container, by e.g. putting a .crt (not .pem) certificate at /usr/local/share/ca-certificates and running update-ca-certificates.
  • Check the parameters you used to create and attached the datacenter by running the following commands
export OPENMANO_TENANT=osm
openmano datacenter-list
openmano datacenter-list <DATACENTER_NAME> -vvv
  • If all seems right, maybe the password was wrong. Try to detach and delete the datacenter, and then create and attach it again with the right password.
openmano datacenter-detach openstack-site
openmano datacenter-delete openstack-site
openmano datacenter-create openstack-site http://10.10.10.11:5000/v2.0 --type openstack --description "OpenStack site"
openmano datacenter-attach openstack-site --user=admin --password=userpwd --vim-tenant-name=admin

Deployment fails with the error message "VIM Exception vimconnUnexpectedResponse Unauthorized: The request you have made requieres authentication. (HTTP 401)"

Follow the same instructions as for the error "Not possible to get_networks_list from VIM: AuthorizationFailure: Authorization Failed: The resource could not be found. (HTTPS: 404)"

OSM RO service fails to start with a message "DATABASE wrong version"

Q. OSM RO service (osm-ro service in RO container) fails to start and logs show "DATABASE wrong version" 

2016-11-02T17:19:51 CRITICAL  openmano openmanod:268 DATABASE wrong version '0.15'.
Try to upgrade/downgrade to version '0.16' with 'database_utils/migrate_mano_db.sh'

A. The reason is that the RO has been upgraded with a new version that requires a new database version. To upgrade the database version, run database_utils/migrate_mano_db.sh and provide credentials if needed (by default database user is 'mano', and database password is 'manopw')

Deployment fails with the message Error creating image at VIM 'xxxx': Cannot create image without location

The reason of the failure is that ther is a mismatch between image names (and checksum) at OSM VNFD and at VIM. Basically the image is not present at VIM.

To fix it, you should add the image at VIM and ensure that it is visible for the VIM credentials provided to RO. At RO container you can list the VIM images using these credentialas easily with the command: 

openmano vim-image-list --datacenter <xxxxx>
Retrieved from "http:///wikipub/index.php?title=Technical_FAQ_(Release_THREE)&oldid=1668"