Same situation in the puppet-agent.log (node-1, 'slave-02_controller'):
(/Stage[main]/Osnailyfacter::Cluster_ha/Nova_floating_range[10.108.6.128-10.108.6.254]) Could not evaluate: Authentication failed with response code 504
Same situation in rabbitmq.log with connectivity errors:
2014-09-05T00:23:03.526999+01:00 notice: {amqp_error,connection_forced,
2014-09-05T00:23:03.526999+01:00 notice: "broker forced connection closure with reason 'shutdown'",none}
2014-09-05T00:23:13.534687+01:00 notice: =INFO REPORT==== 4-Sep-2014::23:23:12 ===
2014-09-05T00:23:13.534812+01:00 notice: Halting Erlang VM
Deployment of node-5 'slave-05_compute' failed before it even started (there is no puppet-agent.log on the node)
Also, while I was examining the logs, Fuel-UI shown that node-3 and node-5 went offline for a few minutes. But, actually, node-3 and node-5 was working all the time (I open VNC on it via vitr-manager and my session to the nodes wasn't broken)
Reproduced on system test 'deploy_ha': jenkins- product. srt.mirantis. net:8080/ view/0_ master_ swarm/job/ master_ fuelmain. system_ test.ubuntu. thread_ 5/151/
http://
Same situation in the puppet-agent.log (node-1, 'slave- 02_controller' ): main]/Osnailyfa cter::Cluster_ ha/Nova_ floating_ range[10. 108.6.128- 10.108. 6.254]) Could not evaluate: Authentication failed with response code 504
(/Stage[
Same situation in rabbitmq.log with connectivity errors: 05T00:23: 03.526999+ 01:00 notice: {amqp_error, connection_ forced, 05T00:23: 03.526999+ 01:00 notice: "broker forced connection closure with reason 'shutdown'",none} 05T00:23: 13.534687+ 01:00 notice: =INFO REPORT==== 4-Sep-2014: :23:23: 12 === 05T00:23: 13.534812+ 01:00 notice: Halting Erlang VM
2014-09-
2014-09-
2014-09-
2014-09-
Deployment of node-5 'slave-05_compute' failed before it even started (there is no puppet-agent.log on the node)
Also, while I was examining the logs, Fuel-UI shown that node-3 and node-5 went offline for a few minutes. But, actually, node-3 and node-5 was working all the time (I open VNC on it via vitr-manager and my session to the nodes wasn't broken)