Technical FAQ (Release THREE) - Revision history

Garciadeblas: Garciadeblas moved page Technical FAQ to Technical FAQ (Release THREE): Outdated

2018-05-28T13:53:32Z

Garciadeblas moved page Technical FAQ to Technical FAQ (Release THREE): Outdated

← Older revision	Revision as of 13:53, 28 May 2018
(No difference)

Fernandezca: Mispelled command

2018-05-10T13:27:00Z

Mispelled command

← Older revision		Revision as of 13:27, 10 May 2018
Line 106:		Line 106:
	283 down 10.44.127.228 juju-ed3163-283 trusty Running		283 down 10.44.127.228 juju-ed3163-283 trusty Running

	# Example: juju machine~~-remove~~ 260		# Example: juju remove-machine 260
	juju machine~~-remove~~ ${"machine" whose ip is related to juju_instance_id} --force		juju remove-machine ${"machine" whose ip is related to juju_instance_id} --force

	# Start Juju in the juju controller		# Start Juju in the juju controller

Fernandezca: Solution to fully loaded VCA containers where also Juju controller ceased to run

2018-04-18T16:02:10Z

Solution to fully loaded VCA containers where also Juju controller ceased to run

Show changes

Garciadeblas at 08:39, 13 July 2017

2017-07-13T08:39:49Z

@@ Line 1: / Line 1: @@
 == "Instantiation failed", but VMs and networks were successfully created ==
@@ Line 30: / Line 21: @@
 '''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.
 == 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)" ==

Garciadeblas: /* Connection error: not possible to contact OPENMANO-SERVER (openmanod) */

2017-07-13T08:39:32Z

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

← Older revision		Revision as of 08:39, 13 July 2017
Line 1:		Line 1:
	== ~~Connection~~ error: not possible to contact OPENMANO-SERVER (openmanod) ==		== SO connection error: not possible to contact OPENMANO-SERVER (openmanod) ==

	'''Q'''. ~~After following the steps carefully as stated in [[OSM Release TWO]] web page, I tried to instantiate the Network Service. All seems correct until the last phase, when I get~~ an ~~error~~ in ~~the UI. I connected to the SO-ub container, opened~~ the SO CLI ~~and run commands below~~:		'''Q'''. The NS operational data of an instantiated NS in the SO CLI shows "Connection error: not possible to contact OPENMANO-SERVER (openmanod)"
	~~$ lxc exec SO-ub~~ -~~- bash~~
	~~root@SO-ub:~# /usr/rift/rift-shell -r -i /usr/rift -a /usr/rift/.artifacts -- rwcli --rift_var_root /usr/rift/var/rift~~ (~~user: admin; pwd: admin~~)
	~~rift# show ns-instance-opdata nsr~~

	The last command allows getting a more comprehensive view about what it is happening. In the last operational-events field, namely "ns-field", details say: "Connection error: not possible to contact OPENMANO-SERVER (openmanod)". I do not know how to fix the problem. I have checked all the previous steps and they seem they are correct.		'''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.

	'''A'''. ~~First, please~~ check connectivity 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		$ lxc exec RO -- bash
	root@SO-ub:~# service osm-ro status		root@SO-ub:~# service osm-ro status

Garciadeblas: /* 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)" */

2017-06-26T14:33:36Z

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)"

← Older revision		Revision as of 14:33, 26 June 2017
Line 38:		Line 38:
	== 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)" ==		== 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)".		'''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		'''A'''. The cause is that Openstack has not been properly added to openmano with the right credentials

Garciadeblas at 14:23, 26 June 2017

2017-06-26T14:23:44Z

← Older revision		Revision as of 14:23, 26 June 2017
Line 35:		Line 35:

	'''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.		'''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.

			== 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>

Garciadeblas: /* "Instantiation failed" and VMs and network were not created at VIM */

2017-05-16T16:27:37Z

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

← Older revision		Revision as of 16:27, 16 May 2017
Line 32:		Line 32:
	== "Instantiation failed" and VMs and network were not created at VIM ==		== "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 '''		'''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'''. ~~Typically you will be~~ hitting a ~~timeout issue in the SO. Although we are working in providing better feedback, below you can find a detailed explanation.~~		'''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.

	~~During instantiation, two timeouts can expire:~~
	* SO-RO timeout, caused ~~because~~ the ~~creation~~ of ~~VMs and networks~~ from the RO to ~~the VIMs takes too long. In some cases, all VMs and networks are created in~~ the VIM~~; however, the instantiation might still reach an SO-RO timeout if not all VNFs have a management IP address.~~
	* SO-VCA timeout, caused because the ~~VNF configuration via Juju charms takes too long.~~

	~~Recommendations:~~
	* Check SO logs, specifically "rift.log" to find out what timeout you might be hitting.
	* In case of ~~a SO-VCA timeout, connect to VCA container and check "juju status".~~
	* In case of a SO-RO timeout, check in the VIM if the VMs and networks ~~were created. If they were created at~~ the ~~VIM, you might still get a failed NS instantiation due~~ to ~~a SO-RO timeout if VNFs do not get an IP address in~~ the ~~management interface. In that case, check below~~.

Garciadeblas: /* "Instantiation failed", but VMs and networks were successfully created */

2017-05-16T16:25:18Z

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

← Older revision		Revision as of 16:25, 16 May 2017
Line 25:		Line 25:
	* 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.		* 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. ~~Then~~ connect to VCA container and check "juju status".		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		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 ==		== "Instantiation failed" and VMs and network were not created at VIM ==

Garciadeblas: /* "Instantiation failed" without additional information */

2017-05-16T16:24:34Z

"Instantiation failed" without additional information

← Older revision		Revision as of 16:24, 16 May 2017
Line 28:		Line 28:
	lxc exec VCA -- juju status		lxc exec VCA -- juju status

	== "Instantiation failed" ~~without additional information~~ ==		== "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.'''		'''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 '''

	'''A'''. Typically you will be hitting a timeout issue in the SO. Although we are working in providing better feedback, below you can find a detailed explanation.		'''A'''. Typically you will be hitting a timeout issue in the SO. Although we are working in providing better feedback, below you can find a detailed explanation.