1. Bug is not reproduced sometimes on "bad" environments.
2. Bug cannot be reproduced on "good" environments. I have tried to deploy a "bad" environment three times and failed to reproduce the bug even after several reboots.
3. Upstart logs modification time shows us that there are two groups of network intefaces that are brought up during different time intervals. Some services are started between these intervals, so ones depending on the latter group would fail.
( http://paste.openstack.org/show/487418/ )
4. Adding "sleep 5" inside /etc/network/if-up.d/upstart significantly reduces the chance to hit this bug.
5. You can start corosync manually in case of failure.
So far known facts:
1. Bug is not reproduced sometimes on "bad" environments. paste.openstack .org/show/ 487418/ ) if-up.d/ upstart significantly reduces the chance to hit this bug.
2. Bug cannot be reproduced on "good" environments. I have tried to deploy a "bad" environment three times and failed to reproduce the bug even after several reboots.
3. Upstart logs modification time shows us that there are two groups of network intefaces that are brought up during different time intervals. Some services are started between these intervals, so ones depending on the latter group would fail.
( http://
4. Adding "sleep 5" inside /etc/network/
5. You can start corosync manually in case of failure.