openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #13579
Re: Additional compute node network issues - rpc timeout
Thanks for your reply Chris. I checked both and nither firewall rules are
in the war nor there is the control_exchange in nova.conf. Just to confirm:
for a single host network setup, nova-network is supposed to be setup only
on the cloud controller and compute nodes should only run nova-compute. Is
this correct?
On Fri, Jun 22, 2012 at 10:36 PM, Chris Wright <chrisw@xxxxxxxxxxxx> wrote:
> * Derek Eli (derek.eli82@xxxxxxxxx) wrote:
> > I am having issues with spawning a VM which gets scheduled to a non cloud
> > controller node, running nova-compute only. It fails with a nerwork
> > configuration error. Looking at logs reveals that it was an rpc timeout
> > error. Further investigations (nova-network logs) reveal that the
> > nova-network tried to send a message to network.nova2 queue and it never
> > received a response and times out, hence, the compute node never
> receives a
> > reply and times out. doing a rabbitmqctl shows no queue named
> network.nova2.
>
> firewall rules on cloud controller node in the way?
>
> nova.conf not matching (i.e. one has control_exchange="nova2" in it)?
>
References