Comment 2 for bug 1346192

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

According to logs, the issue likely caused by 1.3.0 heartbeat patch
2014-07-20T01:12:26.671589 node-1 ./node-1.test.domain.local/rabbitmq.log:2014-07-20T01:12:26.671589+00:00 err: =ERROR REPORT==== 20-
Jul-2014::01:12:24 ===
2014-07-20T01:12:26.671589 node-1 ./node-1.test.domain.local/rabbitmq.log:2014-07-20T01:12:26.671589+00:00 err: {heartbeat_timeout,ru
nning}
2014-07-20T01:15:08.479341 node-1 ./node-1.test.domain.local/rabbitmq.log:2014-07-20T01:15:08.479341+00:00 err: connection_closed_abr
uptly
2014-07-20T01:15:08.479341 node-1 ./node-1.test.domain.local/rabbitmq.log:2014-07-20T01:15:08.479341+00:00 err: =WARNING REPORT==== 2
0-Jul-2014::01:15:08 ===
2014-07-20T01:17:13.352629 node-1 ./node-1.test.domain.local/puppet-apply.log:2014-07-20T01:17:13.352629+00:00 err: (/Stage[main]/Osn
ailyfacter::Cluster_ha/Nova_floating_range[10.108.11.128-10.108.11.254]) Could not evaluate: Oops - not sure what happened: 757: unexp
ected token at '<html><body><h1>504 Gateway Time-out</h1>
2014-07-20T01:17:13.352749 node-1 ./node-1.test.domain.local/puppet-apply.log:2014-07-20T01:17:13.352749+00:00 err: (/Stage[main]/Osn
ailyfacter::Cluster_ha/Nova_floating_range[10.108.11.128-10.108.11.254]) The server didn't respond in time.