Ask Your Question
0

second compute node can't find images

asked 2014-07-14 03:02:18 -0500

apanagiotou gravatar image

Hello, I installed openstack icehouse with nova-network+multi-host on 2 machines(1 controller, 1 compute). Everything was OK. Then i installed a second compute node. Now when I create an instance on the 2nd compute node it goes to error state and the nova-compute.log is:

2014-07-14 09:50:14.555 17693 TRACE nova.compute.manager [instance: ee2552a3-7cac-41ec-bf21-3adb37d1b12d] ImageNotFound: Image c01a2fae-286d-42ce-b6f9-e10995b58563 could not be found.

The second compute node can't find images(the first compute node can). Images backend is file(on controller).

Any help?

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2014-07-14 05:03:24 -0500

foexle gravatar image

Hi,

check your nova.conf if your glance settings are correct.

glance_api_servers=https://images.xxxxx:9292
glance_host=https://images.xxxx:9292
glance_protocol=https

In addition check your glance log file if you see any errors.

Cheers Heiko

edit flag offensive delete link more

Comments

The nova.conf are identical on both compute nodes. The first finds the images,but the second is not. How is that possible? Is there any chance that it is network/bridge problem?

No errors on glance log

apanagiotou gravatar imageapanagiotou ( 2014-07-14 05:11:56 -0500 )edit

do you tryed from comp2

nmap <glance_host> -p 9292

Is that valid ? So you need to check if comp2 can communicate with glance server

foexle gravatar imagefoexle ( 2014-07-14 06:27:09 -0500 )edit

nmap 192.168.1.32 -p 9292

Starting Nmap 6.40 ( http://nmap.org ) at 2014-07-14 13:28 CEST Nmap scan report for 192.168.1.32 Host is up (0.00013s latency). PORT STATE SERVICE 9292/tcp open unknown MAC Address: V4:UP:5J:O9:DJ (VMware)

Nmap done: 1 IP address (1 host up) scanned in 0.48 seconds

apanagiotou gravatar imageapanagiotou ( 2014-07-14 06:29:48 -0500 )edit

If they are identical did you at least change the IP address information to match the new host within nova.conf? Can the new compute node reach glance:

telnet controllerIP 9292

Are you using DNS? Can you resolve the hostnames, did you setup your hosts file the same on the new node(if you aren't using DNS.)

mpetason gravatar imagempetason ( 2014-07-14 10:37:54 -0500 )edit

1) nova.conf is OK 2) I can reach glance via telnet. 3) I use /etc/hosts and it is all right.

It's so strange. I guess I have to re-setup a second compute node.

apanagiotou gravatar imageapanagiotou ( 2014-07-14 12:20:22 -0500 )edit
0

answered 2015-04-22 06:10:49 -0500

Ashish Chandra gravatar image

Hi there, I had the same issue and was troubled for a lot of time. But the solution was very simple. First please check,if you have multiple images in different controller nodes, if it there please delete that, and let only one image stay there.

The issue will be fixed.

edit flag offensive delete link more

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: 2014-07-14 03:02:18 -0500

Seen: 1,251 times

Last updated: Jul 14 '14