Nova Meta Data service stack traces with error: [Errno 113] No route to host all the time
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
New
|
High
|
Unassigned |
Bug Description
The Nova Meta Data service is full of stack traces. Largely all about no route to host. These can be seen like this:
2014-04-27 19:10:41.463 30617 INFO nova.metadata.
Traceback (most recent call last):
File "/usr/local/
func(*args, **kwargs)
File "/usr/local/
proto.
File "/usr/lib/
self.handle()
File "/usr/lib/
self.
File "/usr/local/
self.
File "/usr/lib/
data = self._sock.
File "/usr/local/
return fd.recv(buflen, flags)
error: [Errno 113] No route to host
While these are mostly non fatal, it appears sometimes these trigger a crash, causing test runs to fail.
This is happening *a lot*: message:"error: [Errno 113] No route to host" AND (tags:screen-
Changed in nova: | |
importance: | Undecided → High |
tags: | added: network |
Do you use neutron- metadata- proxy?
Post nova.conf from controller and compute node
Show your fierwall rules from controller and compute node