Controller node - nova services stop after one compute node starts
Hello,
I am using devstack to deploy a 2 nodes setup (one controller/network/compute and one compute). The controller node starts correctly and I can launch instances without any problem:
All the services are started:
nova service-list
+----+------------------+---------------------------+----------+---------+-------+
| Id | Binary | Host | Zone | Status | State | Updated_at
+----+------------------+---------------------------+----------+---------+-------+
| 1 | nova-conductor | arbiter | internal | enabled | up | 2015-03-27T18:31:36. |
| 3 | nova-cert | arbiter | internal | enabled | up | 2015-03-27T18:31:29. |
| 4 | nova-scheduler | arbiter | internal | enabled | up | 2015-03-27T18:31:32. |
| 5 | nova-compute | arbiter | nova | enabled | up | 2015-03-27T18:31:27. |
| 6 | nova-consoleauth | arbiter | internal | enabled | up | 2015-03-27T18:31:31. |
+----+------------------+---------------------------+----------+---------+-------+
But when my compute node is deploying itself, after some time:
nova service-list
ERROR (ClientException): The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-83ea8582-fc02-48d9-a939-040b1eb9fcf4)
And when the compute node is completely deployed:
nova service-list
+----+--------------+--------------------------+------+---------+-------+
| Id | Binary | Host | Zone | Status | State | Updated_at | |
+----+--------------+--------------------------+------+---------+-------+
| 1 | nova-compute | zepler | nova | enabled | up | 2015-03-27T18:31:56. | - |
+----+--------------+--------------------------+------+---------+-------+
It seems that the compute node stops all the nova services in the Controller node. How is that possible?
I have MULTI_HOST=True
for both my controller and compute node in the local.conf file.
Thank you for any suggestions :)