* Derek Eli ([email protected]) 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)? _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
