© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Artem, corosync logs show that cluster was affected by network partitioning. This is why all the resources on the node-1 node were stopped by pacemaker and thus haproxy returned error 504. And we are not going to handle 504 error for keystone in neutron providers as keystone must be ready by the moment neutron wants to create networks.