Ask Your Question
0

openstack resize problem

asked 2017-04-12 20:39:15 -0500

vblando gravatar image

updated 2017-04-12 20:39:38 -0500

A weird thing happened today, I was resizing some instances and it wont proceed, after inspecting the logs, I saw that it was trying to move the instance to a non-existent compute


2017-04-13 08:31:59.789 144207 ERROR oslo_messaging.rpc.dispatcher Command: ssh 172.60.60.21 mkdir -p /var/lib/nova/instances/785e7c09-3bf9-46f2-b052-f7c5e b6c1c98 2017-04-13 08:31:59.789 144207 ERROR oslo_messaging.rpc.dispatcher Exit code: 255 2017-04-13 08:31:59.789 144207 ERROR oslo_messaging.rpc.dispatcher Stdout: u'' 2017-04-13 08:31:59.789 144207 ERROR oslo_messaging.rpc.dispatcher Stderr: u'ssh: connect to host 172.60.60.21 port 22: Connection timed out\r\n'

2017-04-13 08:31:59.789 144207 ERROR oslo_messaging.rpc.dispatcher

That IP does not exist on my network. How did that happened?

Any ideas?

edit retag flag offensive close merge delete

Comments

Perhaps Nova has this host in its database even though it doesn't exist (anymore). What do you get when running openstack compute service list?

Bernd Bausch gravatar imageBernd Bausch ( 2017-04-12 23:56:26 -0500 )edit

that list will give me the hostname, which are correct, but nova resize uses IP, I need to know where is it looking for the compute list

vblando gravatar imagevblando ( 2017-04-13 09:42:13 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-04-13 06:36:52 -0500

Laurent_bcn gravatar image

updated 2017-04-13 06:37:54 -0500

A resize cannot be done on the same host.Nova is trying to contact an other host with passwordless authentication for making the resize.

Make sure that all your Nova compute can contact each others with ssh under the nova account.

Check all your /etc/hosts to verify the mapping ip/hostname

edit flag offensive delete link more

Comments

I have no problem with resize, i already set nova to connect to all instances without password, my question is actually why is it trying to connect to a non-existent host.

vblando gravatar imagevblando ( 2017-04-13 09:43:41 -0500 )edit

ok so you can check it this ghost ip is stored in the controller database :

1- connect to the msyql engine

2- switch to nova database : use nova;

3- Display all nova IP compute nodes : select host_ip from compute_nodes;

Laurent_bcn gravatar imageLaurent_bcn ( 2017-04-13 11:21:23 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2017-04-12 20:39:15 -0500

Seen: 379 times

Last updated: Apr 13 '17