[CI down] pingtest fails when accessing to OpenStack APIs
Bug #1596758 reported by
Emilien Macchi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Pradeep Kilambi |
Bug Description
Currently, ha and upgrade jobs are broken during pingtest, that fails to reach OpenStack API:
It sounds like Pacemaker is in a bad shape during the deployment. I also noticed RabbitMQ down.
Need more investigation.
summary: |
- pingtest fails when accessing to OpenStack APIs + [CI down] RabbitMQ fails to form a cluster |
Changed in tripleo: | |
assignee: | nobody → Pradeep Kilambi (pkilambi) |
status: | Confirmed → In Progress |
tags: | removed: alert |
To post a comment you must log in.
The crucial part is here, RabbitMQ fails to form a cluster:
Jun 27 21:48:50 [13170] overcloud- controller- 0 crmd: notice: te_rsc_command: Initiating action 71: start rabbitmq_start_0 on overcloud- controller- 0 (local) controller- 0 crmd: info: do_lrm_rsc_op: Performing key=71: 17:0:61c3eb8c- c41b-47ed- 85a4-d2051d130e a9 op=rabbitmq_start_0 controller- 0 lrmd: info: log_execute: executing - rsc:rabbitmq action:start call_id:64 controller- 0 cib: info: cib_process_ request: Completed cib_modify operation for section status: OK (rc=0, origin= overcloud- controller- 2/crmd/ 39, version=0.31.3) controller- 0 crmd: info: throttle_ handle_ load: Moderate CPU load detected: 0.840000 controller- 0 crmd: info: throttle_ send_command: New throttle mode: 0010 (was 0100) cluster( rabbitmq) [23989] : 2016/06/27_21:48:51 INFO: RabbitMQ server is not running cluster( rabbitmq) [23989] : 2016/06/27_21:48:51 INFO: Joining existing cluster with [ rabbit@ overcloud- controller- 2 ] nodes. cluster( rabbitmq) [23989] : 2016/06/27_21:48:51 INFO: Waiting for server to start controller- 0 cib: info: cib_process_ping: Reporting our current digest to overcloud- controller- 0: 0d5b3d9a1e8a9c7 820e450dbd39a22 80 for 0.31.3 (0x27e10e0 0) controller- 0 attrd: info: attrd_peer_update: Setting rmq-node- attr-rabbitmq[ overcloud- controller- 0]: (null) -> rabbit@ overcloud- controller- 0 from overcloud- controller- 0 controller- 0 cib: info: cib_perform_op: Diff: --- 0.31.3 2 controller- 0 cib: info: cib_perform_op: Diff: +++ 0.31.4 (null) controller- 0 cib: info: cib_perform_op: + /cib: @num_updates=4 controller- 0 cib: info: cib_perform_op: ++ /cib/status/ node_state[ @id='1' ]/transient_ attributes[ @id='1' ]/instance_ attributes[ @id='status- 1']: <nvpair id="status- 1-rmq-node- attr-rabbitmq" name="rmq- node-attr- rabbitmq" value=" rabbit@ overcloud- controller- 0"/> controller- 0 cib: info: cib_process_ request: Completed cib_modify operation for section status: OK (rc=0, origin= overcloud- controller- 2/attrd/ 26, version=0.31.4) controller- 0 crmd: notice: abort_transitio n_graph: Transition aborted by status- 1-rmq-node- attr-rabbitmq, rmq-node- attr-rabbitmq= rabbit@ overcloud- controller- 0: Transient attribute change (create cib=0.31.4, source= abort_unless_ down:319, path=/cib/ status/ node_state[ @id='1' ]/transient_ attributes[ @id='1' ]/instance_ attributes[ @id='status- 1'], 0) controller- 0 cib: info: cib_process_ request: Forwarding cib_modify operation for section nodes to master (origin= local/crm_ attribute/ 4) controller- 0 cib: info: cib_perform_op: Diff: -...
Jun 27 21:48:50 [13170] overcloud-
Jun 27 21:48:50 [13167] overcloud-
Jun 27 21:48:50 [13165] overcloud-
Jun 27 21:48:51 [13170] overcloud-
Jun 27 21:48:51 [13170] overcloud-
rabbitmq-
rabbitmq-
rabbitmq-
Jun 27 21:48:55 [13165] overcloud-
Jun 27 21:48:57 [13168] overcloud-
Jun 27 21:48:57 [13165] overcloud-
Jun 27 21:48:57 [13165] overcloud-
Jun 27 21:48:57 [13165] overcloud-
Jun 27 21:48:57 [13165] overcloud-
Jun 27 21:48:57 [13165] overcloud-
Jun 27 21:48:57 [13170] overcloud-
Jun 27 21:48:57 [13165] overcloud-
Jun 27 21:48:57 [13165] overcloud-