Common issues and troubleshooting - Revision history

Ramonsalguer at 17:19, 17 February 2021

2021-02-17T17:19:06Z

← Older revision		Revision as of 17:19, 17 February 2021
Line 1:		Line 1:
			'''THIS PAGE IS DEPRECATED'''. OSM User Guide has been moved to a new location: '''https://osm.etsi.org/docs/user-guide/'''

			---

	__TOC__		__TOC__

Fleischmann: Update with iptable changes in manual reconfigure juju

2019-12-12T11:22:50Z

Update with iptable changes in manual reconfigure juju

@@ Line 352: / Line 352: @@
 docker stack rm osm
 docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm
 </nowiki>

Garciadeblas at 14:50, 16 October 2019

2019-10-16T14:50:58Z

← Older revision		Revision as of 14:50, 16 October 2019
Line 289:		Line 289:

	In extraordinary situations, the output of "juju status" could show pending units that should have been removed when deleting a NS. In those situations, you can clean up VCA by following the procedure below:		In extraordinary situations, the output of "juju status" could show pending units that should have been removed when deleting a NS. In those situations, you can clean up VCA by following the procedure below:
	juju status		juju status -m <NS_ID>
	juju remove-application <application>		juju remove-application -m <NS_ID> <application>
	juju resolved <unit> --no-retry # You'll likely have to run it several times, as it will probably have an error in the next queued hook.Once the last hook is marked resolved, the charm will continue its removal		juju resolved -m <NS_ID> <unit> --no-retry # You'll likely have to run it several times, as it will probably have an error in the next queued hook.Once the last hook is marked resolved, the charm will continue its removal

	The following page also shows [https://docs.jujucharms.com/2.1/en/charms-destroy how to remove different Juju objects]		The following page also shows [https://docs.jujucharms.com/2.1/en/charms-destroy how to remove different Juju objects]
Line 299:		Line 299:
	To dump the Juju debug-logs, run this command:		To dump the Juju debug-logs, run this command:
	juju debug-log --replay --no-tail > juju-debug.log		juju debug-log --replay --no-tail > juju-debug.log
			juju debug-log --replay --no-tail -m <NS_ID>
			juju debug-log --replay --no-tail -m <NS_ID> --include <UNIT>

	====Manual recovery of Juju====		====Manual recovery of Juju====

Tierno: /* NBI Errors */

2019-10-03T14:16:13Z

NBI Errors

← Older revision		Revision as of 14:16, 3 October 2019
Line 370:		Line 370:
	* '''ERROR''': NBI always return "UNAUTHORIZED" Cannot login neither with UI nor with CLI. CLI shows error "can't find a default project for this user" or "project admin not allowed for this user".		* '''ERROR''': NBI always return "UNAUTHORIZED" Cannot login neither with UI nor with CLI. CLI shows error "can't find a default project for this user" or "project admin not allowed for this user".
	* '''CAUSE''': Normally after a migration to release 6.0.2 There is a slight incompatibility with users creared from older versions		* '''CAUSE''': Normally after a migration to release 6.0.2 There is a slight incompatibility with users creared from older versions
	* '''SOLUTION''': Delete user admin and reboot NBI so that a new compatible user is created~~. Run~~ these commands: "curl --insecure https://localhost:9999/osm/test/db-clear/users~~"; "~~docker service update osm_nbi --force";		* '''SOLUTION''': Delete user admin and reboot NBI so that a new compatible user is created by running these commands:
			curl --insecure https://localhost:9999/osm/test/db-clear/users
			docker service update osm_nbi --force

	==Checking the logs==		==Checking the logs==

Tierno: /* NBI Errors */

2019-10-03T14:14:55Z

NBI Errors

← Older revision		Revision as of 14:14, 3 October 2019
Line 367:		Line 367:

	===NBI Errors===		===NBI Errors===
	====~~can't find a default project for this user~~====		====Cannot login after migration to 6.0.2====
	* '''ERROR''': NBI always return "UNAUTHORIZED" Cannot login neither with UI nor with CLI. CLI shows error "can't find a default project for this user" or "project admin not allowed for this user".		* '''ERROR''': NBI always return "UNAUTHORIZED" Cannot login neither with UI nor with CLI. CLI shows error "can't find a default project for this user" or "project admin not allowed for this user".
	* '''CAUSE''': Normally after a migration to release 6.0.2 There is a slight incompatibility with users creared from older versions		* '''CAUSE''': Normally after a migration to release 6.0.2 There is a slight incompatibility with users creared from older versions

Tierno: /* NBI Errors */

2019-10-03T14:13:55Z

NBI Errors

← Older revision		Revision as of 14:13, 3 October 2019
Line 368:		Line 368:
	===NBI Errors===		===NBI Errors===
	====can't find a default project for this user====		====can't find a default project for this user====
	* '''ERROR''': NBI always return "UNAUTHORIZED" "can't find a default project for this user" or "project admin not allowed for this user"		* '''ERROR''': NBI always return "UNAUTHORIZED" Cannot login neither with UI nor with CLI. CLI shows error "can't find a default project for this user" or "project admin not allowed for this user".
	* '''CAUSE''': Normally after a migration to release 6.0.2 There is a slight incompatibility with users creared from older versions		* '''CAUSE''': Normally after a migration to release 6.0.2 There is a slight incompatibility with users creared from older versions
	* '''SOLUTION''': Delete user admin and reboot NBI so that a new compatible user is created. Run these commands: "curl --insecure https://localhost:9999/osm/test/db-clear/users"; "docker service update osm_nbi --force";		* '''SOLUTION''': Delete user admin and reboot NBI so that a new compatible user is created. Run these commands: "curl --insecure https://localhost:9999/osm/test/db-clear/users"; "docker service update osm_nbi --force";

Tierno: /* can't find a default project for this user */

2019-10-02T08:43:13Z

can't find a default project for this user

← Older revision		Revision as of 08:43, 2 October 2019
Line 368:		Line 368:
	===NBI Errors===		===NBI Errors===
	====can't find a default project for this user====		====can't find a default project for this user====
	* '''ERROR''': NBI always return "UNAUTHORIZED" "can't find a default project for this user"		* '''ERROR''': NBI always return "UNAUTHORIZED" "can't find a default project for this user" or "project admin not allowed for this user"
	* '''CAUSE''': Normally after a migration to release 6.0.2 There is a slight incompatibility with users creared from older versions		* '''CAUSE''': Normally after a migration to release 6.0.2 There is a slight incompatibility with users creared from older versions
	* '''SOLUTION''': Delete user admin and reboot NBI so that a new compatible user is created. Run these commands: "curl --insecure https://localhost:9999/osm/test/db-clear/users"; "docker service update osm_nbi --force";		* '''SOLUTION''': Delete user admin and reboot NBI so that a new compatible user is created. Run these commands: "curl --insecure https://localhost:9999/osm/test/db-clear/users"; "docker service update osm_nbi --force";

Tierno: /* Instantiation Errors */

2019-09-18T14:08:11Z

Instantiation Errors

← Older revision		Revision as of 14:08, 18 September 2019
Line 365:		Line 365:
	* '''CAUSE''': Normally a migration from release FIVE do not set properly the env for LCM		* '''CAUSE''': Normally a migration from release FIVE do not set properly the env for LCM
	* '''SOLUTION''': Ensure variable '''OSMLCM_VCA_PUBKEY''' is properly set at file ''/etc/osm/docker/lcm.env''. The value must mutch with the output of this command ''cat $HOME/.local/share/juju/ssh/juju_id_rsa.pub''. If not, add or change it. Restart OSM, or just LCM service with ''docker service update osm_lcm --force --env-add OSMLCM_VCA_PUBKEY="<value>" ''		* '''SOLUTION''': Ensure variable '''OSMLCM_VCA_PUBKEY''' is properly set at file ''/etc/osm/docker/lcm.env''. The value must mutch with the output of this command ''cat $HOME/.local/share/juju/ssh/juju_id_rsa.pub''. If not, add or change it. Restart OSM, or just LCM service with ''docker service update osm_lcm --force --env-add OSMLCM_VCA_PUBKEY="<value>" ''

			===NBI Errors===
			====can't find a default project for this user====
			* '''ERROR''': NBI always return "UNAUTHORIZED" "can't find a default project for this user"
			* '''CAUSE''': Normally after a migration to release 6.0.2 There is a slight incompatibility with users creared from older versions
			* '''SOLUTION''': Delete user admin and reboot NBI so that a new compatible user is created. Run these commands: "curl --insecure https://localhost:9999/osm/test/db-clear/users"; "docker service update osm_nbi --force";

	==Checking the logs==		==Checking the logs==

Tierno: /* Manual recovery of Juju */

2019-09-10T14:12:43Z

Manual recovery of Juju

← Older revision		Revision as of 14:12, 10 September 2019
Line 342:		Line 342:
	sudo sed -i 's/^OSMMON_VCA_SECRET.*$/OSMMON_VCA_SECRET='$juju_password'/' /etc/osm/docker/mon.env		sudo sed -i 's/^OSMMON_VCA_SECRET.*$/OSMMON_VCA_SECRET='$juju_password'/' /etc/osm/docker/mon.env
	sudo sed -i 's/^OSMLCM_VCA_SECRET.*$/OSMLCM_VCA_SECRET='$juju_password'/' /etc/osm/docker/lcm.env		sudo sed -i 's/^OSMLCM_VCA_SECRET.*$/OSMLCM_VCA_SECRET='$juju_password'/' /etc/osm/docker/lcm.env

			juju_pubkey=$(cat $HOME/.local/share/juju/ssh/juju_id_rsa.pub)
			sudo sed -i 's/^OSMLCM_VCA_PUBKEY.*$/OSMLCM_VCA_PUBKEY='$juju_pubkey'/' /etc/osm/docker/mon.env
			sudo sed -i 's/^OSMLCM_VCA_PUBKEY.*$/OSMLCM_VCA_PUBKEY='$juju_pubkey'/' /etc/osm/docker/lcm.env

	#Restart OSM stack		#Restart OSM stack

Tierno: /* File juju_id_rsa.pub not found */

2019-08-22T09:35:15Z

File juju_id_rsa.pub not found

← Older revision		Revision as of 09:35, 22 August 2019
Line 360:		Line 360:
	* '''ERROR''': ERROR creating VCA model name 'xxxx': Traceback (most recent call last): File "/usr/lib/python3/dist-packages/osm_lcm/ns.py", line 822, in instantiate await ... [Errno 2] No such file or directory: '/root/.local/share/juju/ssh/juju_id_rsa.pub'		* '''ERROR''': ERROR creating VCA model name 'xxxx': Traceback (most recent call last): File "/usr/lib/python3/dist-packages/osm_lcm/ns.py", line 822, in instantiate await ... [Errno 2] No such file or directory: '/root/.local/share/juju/ssh/juju_id_rsa.pub'
	* '''CAUSE''': Normally a migration from release FIVE do not set properly the env for LCM		* '''CAUSE''': Normally a migration from release FIVE do not set properly the env for LCM
	* '''SOLUTION''': Ensure variable '''OSMLCM_VCA_PUBKEY''' is properly set at file ''/etc/osm/docker/lcm.env''. The value must mutch with the output of this command ''cat $HOME/.local/share/juju/ssh/juju_id_rsa.pub''. If not, add or change it. Restart OSM, or just LCM service with '''docker service update osm_lcm --force --env-add OSMLCM_VCA_PUBKEY="<value>" '''		* '''SOLUTION''': Ensure variable '''OSMLCM_VCA_PUBKEY''' is properly set at file ''/etc/osm/docker/lcm.env''. The value must mutch with the output of this command ''cat $HOME/.local/share/juju/ssh/juju_id_rsa.pub''. If not, add or change it. Restart OSM, or just LCM service with ''docker service update osm_lcm --force --env-add OSMLCM_VCA_PUBKEY="<value>" ''

	==Checking the logs==		==Checking the logs==