So we have this four node Nova cluster running Essex. It has worked fine, but we've added new network interfaces. Openstack has not yet been configured to use them, but changes have been made that allows the system to come up and configure the network in a similar way to before. Now, all of the services seem to be up and running, Rabbit is apparently happy as far as I can tell. Nova-scheduler and nova-compute are running and talking to Rabbit. Now then, whenever I log into any nova node and boot an instance or ten, all instances get started on a single node; always the same node, never any attempt by any of the others to start an instance. I thought this would be a Rabbit problem, but rabbit thinks it's doing fine on all nodes and the cluster is intact. I've even tried completely rebuilding the Rabbit configuration, just in case. If I stop services on the one working node, the other nodes don't even appear to receive messages from either themselves or each other, regardless of Rabbit's supposedly working state.
Any ideas? Any clue how you would even test this to see what's happening? Chris -- Christopher Smith Systems Engineer, Wolfram Research _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
