Mar 13 15:29:04 vm0 lrmd: [2262]: debug: on_msg_perform_op: add an operation operation start[1460] on p_keystone for client 2265, its parameters: crm_feature_set=[3.0.5] os_auth_url=[http://192.168.10.103:5000/v2.0/] os_tenant_name=[demo] config=[/etc/keystone/keystone.conf] os_password=[gkeZe67EBCaF] os_username=[admin] CRM_meta_timeout=[20000]  to the operation list.
Mar 13 15:29:04 vm0 lrmd: [2262]: info: rsc:p_keystone start[1460] (pid 19504)
Mar 13 15:29:06 vm0 lrmd: [2262]: info: Managed p_keystone:start process 19504 exited with return code 0.
Mar 13 15:29:06 vm0 lrmd: [2262]: info: operation start[1460] on p_keystone for client 2265: pid 19504 exited with return code 0
Mar 13 15:29:06 vm0 crmd: [2265]: debug: create_operation_update: do_update_resource: Updating resouce p_keystone after complete start op (interval=0)
Mar 13 15:29:06 vm0 crmd: [2265]: info: process_lrm_event: LRM operation p_keystone_start_0 (call=1460, rc=0, cib-update=3615, confirmed=true) ok
Mar 13 15:29:06 vm0 crmd: [2265]: debug: update_history_cache: Appending start op to history for 'p_keystone'
Mar 13 15:29:06 vm0 crmd: [2265]: info: match_graph_event: Action p_keystone_start_0 (102) confirmed on vm0 (rc=0)
Mar 13 15:29:06 vm0 crmd: [2265]: info: te_rsc_command: Initiating action 5: monitor p_keystone_monitor_30000 on vm0 (local)
Mar 13 15:29:06 vm0 crmd: [2265]: info: do_lrm_rsc_op: Performing key=5:1149:0:cca7f396-8e31-40a7-a2f3-ce95acca4de1 op=p_keystone_monitor_30000 )
Mar 13 15:29:06 vm0 lrmd: [2262]: debug: on_msg_perform_op: add an operation operation monitor[1461] on p_keystone for client 2265, its parameters: CRM_meta_timeout=[30000] os_username=[admin] CRM_meta_name=[monitor] crm_feature_set=[3.0.5] config=[/etc/keystone/keystone.conf] os_tenant_name=[demo] CRM_meta_interval=[30000] os_password=[gkeZe67EBCaF] os_auth_url=[http://192.168.10.103:5000/v2.0/]  to the operation list.
Mar 13 15:29:06 vm0 lrmd: [2262]: info: rsc:p_keystone monitor[1461] (pid 19555)
Mar 13 15:29:07 vm0 lrmd: [2262]: info: Managed p_keystone:monitor process 19555 exited with return code 0.
Mar 13 15:29:07 vm0 lrmd: [2262]: info: operation monitor[1461] on p_keystone for client 2265: pid 19555 exited with return code 0
Mar 13 15:29:07 vm0 crmd: [2265]: debug: create_operation_update: do_update_resource: Updating resouce p_keystone after complete monitor op (interval=30000)
Mar 13 15:29:07 vm0 crmd: [2265]: info: process_lrm_event: LRM operation p_keystone_monitor_30000 (call=1461, rc=0, cib-update=3616, confirmed=false) ok
Mar 13 15:29:07 vm0 crmd: [2265]: debug: update_history_cache: Appending monitor op to history for 'p_keystone'
Mar 13 15:29:07 vm0 crmd: [2265]: info: match_graph_event: Action p_keystone_monitor_30000 (5) confirmed on vm0 (rc=0)
Mar 13 15:29:37 vm0 lrmd: [2262]: debug: rsc:p_keystone monitor[1461] (pid 19957)
Mar 13 15:29:37 vm0 lrmd: [2262]: info: operation monitor[1461] on p_keystone for client 2265: pid 19957 exited with return code 0
Mar 13 15:30:07 vm0 lrmd: [2262]: debug: rsc:p_keystone monitor[1461] (pid 20310)
Mar 13 15:30:37 vm0 lrmd: [2262]: WARN: p_keystone:monitor process (PID 20310) timed out (try 1).  Killing with signal SIGTERM (15).
Mar 13 15:30:37 vm0 lrmd: [2262]: WARN: Managed p_keystone:monitor process 20310 killed by signal 15 [SIGTERM - Termination (ANSI)].
Mar 13 15:30:37 vm0 lrmd: [2262]: WARN: operation monitor[1461] on p_keystone for client 2265: pid 20310 timed out
Mar 13 15:30:37 vm0 crmd: [2265]: ERROR: process_lrm_event: LRM operation p_keystone_monitor_30000 (1461) Timed Out (timeout=30000ms)
Mar 13 15:30:37 vm0 crmd: [2265]: debug: create_operation_update: do_update_resource: Updating resouce p_keystone after Timed Out monitor op (interval=30000)
Mar 13 15:30:37 vm0 crmd: [2265]: debug: update_history_cache: Appending monitor op to history for 'p_keystone'
Mar 13 15:30:37 vm0 crmd: [2265]: info: process_graph_event: Action p_keystone_monitor_30000 arrived after a completed transition
Mar 13 15:30:37 vm0 crmd: [2265]: info: abort_transition_graph: process_graph_event:490 - Triggered transition abort (complete=1, tag=lrm_rsc_op, id=p_keystone_monitor_30000, magic=2:-2;5:1149:0:cca7f396-8e31-40a7-a2f3-ce95acca4de1, cib=0.174.116) : Inactive graph
Mar 13 15:30:37 vm0 crmd: [2265]: WARN: update_failcount: Updating failcount for p_keystone on vm0 after failed monitor: rc=-2 (update=value++, time=1363174237)
Mar 13 15:30:37 vm0 crmd: [2265]: debug: attrd_update_delegate: Sent update: fail-count-p_keystone=value++ for vm0
Mar 13 15:30:37 vm0 crmd: [2265]: debug: attrd_update_delegate: Sent update: last-failure-p_keystone=1363174237 for vm0
Mar 13 15:30:37 vm0 attrd: [2263]: debug: attrd_local_callback: update message from crmd: fail-count-p_keystone=value++
Mar 13 15:30:37 vm0 attrd: [2263]: info: attrd_local_callback: Expanded fail-count-p_keystone=value++ to 412
Mar 13 15:30:37 vm0 attrd: [2263]: debug: attrd_local_callback: New value of fail-count-p_keystone is 412
Mar 13 15:30:37 vm0 attrd: [2263]: notice: attrd_trigger_update: Sending flush op to all hosts for: fail-count-p_keystone (412)
Mar 13 15:30:37 vm0 cib: [2261]: debug: cib_process_xpath: Processing cib_query op for //cib/status//node_state[@id='vm0']//transient_attributes//nvpair[@name='fail-count-p_keystone'] (/cib/status/node_state[1]/transient_attributes/instance_attributes/nvpair[6])
Mar 13 15:30:37 vm0 attrd: [2263]: debug: find_nvpair_attr_delegate: Match <nvpair id="status-vm0-fail-count-p_keystone" name="fail-count-p_keystone" value="411" />
Mar 13 15:30:37 vm0 attrd: [2263]: notice: attrd_perform_update: Sent update 2126: fail-count-p_keystone=412
Mar 13 15:30:37 vm0 attrd: [2263]: debug: attrd_local_callback: update message from crmd: last-failure-p_keystone=1363174237
Mar 13 15:30:37 vm0 attrd: [2263]: debug: attrd_local_callback: New value of last-failure-p_keystone is 1363174237
Mar 13 15:30:37 vm0 attrd: [2263]: notice: attrd_trigger_update: Sending flush op to all hosts for: last-failure-p_keystone (1363174237)
Mar 13 15:30:38 vm0 cib: [2261]: debug: cib_process_xpath: Processing cib_query op for //cib/status//node_state[@id='vm0']//transient_attributes//nvpair[@name='last-failure-p_keystone'] (/cib/status/node_state[1]/transient_attributes/instance_attributes/nvpair[4])
Mar 13 15:30:38 vm0 attrd: [2263]: debug: find_nvpair_attr_delegate: Match <nvpair id="status-vm0-last-failure-p_keystone" name="last-failure-p_keystone" value="1363174143" />

Mar 13 15:30:38 vm0 attrd: [2263]: notice: attrd_perform_update: Sent update 2128: last-failure-p_keystone=1363174237
Mar 13 15:30:38 vm0 attrd: [2263]: debug: attrd_cib_callback: Update 2126 for fail-count-p_keystone=412 passed
Mar 13 15:30:38 vm0 crmd: [2265]: info: abort_transition_graph: te_update_diff:164 - Triggered transition abort (complete=1, tag=nvpair, id=status-vm0-fail-count-p_keystone, name=fail-count-p_keystone, value=412, magic=NA, cib=0.174.117) : Transient attribute: update
Mar 13 15:30:38 vm0 crmd: [2265]: debug: abort_transition_graph: Cause <nvpair id="status-vm0-fail-count-p_keystone" name="fail-count-p_keystone" value="412" />
Mar 13 15:30:38 vm0 attrd: [2263]: debug: attrd_cib_callback: Update 2128 for last-failure-p_keystone=1363174237 passed
Mar 13 15:30:38 vm0 crmd: [2265]: info: abort_transition_graph: te_update_diff:164 - Triggered transition abort (complete=1, tag=nvpair, id=status-vm0-last-failure-p_keystone, name=last-failure-p_keystone, value=1363174237, magic=NA, cib=0.174.118) : Transient attribute: update
Mar 13 15:30:38 vm0 crmd: [2265]: debug: abort_transition_graph: Cause <nvpair id="status-vm0-last-failure-p_keystone" name="last-failure-p_keystone" value="1363174237" />
Mar 13 15:30:38 vm0 pengine: [2264]: WARN: unpack_rsc_op: Processing failed op p_keystone_monitor_30000 on vm0: unknown exec error (-2)
Mar 13 15:30:38 vm0 pengine: [2264]: WARN: unpack_rsc_op: Processing failed op p_keystone_last_failure_0 on vm1: unknown exec error (-2)
Mar 13 15:30:38 vm0 pengine: [2264]: info: native_print:      p_keystone#011(ocf::openstack:keystone):#011Started vm0 FAILED
Mar 13 15:30:38 vm0 pengine: [2264]: info: get_failcount: p_keystone has failed 411 times on vm0
Mar 13 15:30:38 vm0 pengine: [2264]: notice: common_apply_stickiness: p_keystone can fail 999589 more times on vm0 before being forced off
Mar 13 15:30:38 vm0 pengine: [2264]: info: get_failcount: p_keystone has failed INFINITY times on vm1
Mar 13 15:30:38 vm0 pengine: [2264]: WARN: common_apply_stickiness: Forcing p_keystone away from vm1 after 1000000 failures (max=1000000)
Mar 13 15:30:38 vm0 pengine: [2264]: debug: native_assign_node: Assigning vm0 to p_keystone
Mar 13 15:30:38 vm0 pengine: [2264]: notice: RecurringOp:  Start recurring monitor (30s) for p_keystone on vm0
Mar 13 15:30:38 vm0 pengine: [2264]: notice: LogActions: Recover p_keystone#011(Started vm0)
Mar 13 15:30:38 vm0 pengine: [2264]: WARN: unpack_rsc_op: Processing failed op p_keystone_monitor_30000 on vm0: unknown exec error (-2)
Mar 13 15:30:38 vm0 pengine: [2264]: WARN: unpack_rsc_op: Processing failed op p_keystone_last_failure_0 on vm1: unknown exec error (-2)
Mar 13 15:30:38 vm0 pengine: [2264]: info: native_print:      p_keystone#011(ocf::openstack:keystone):#011Started vm0 FAILED
Mar 13 15:30:38 vm0 pengine: [2264]: info: get_failcount: p_keystone has failed 412 times on vm0
Mar 13 15:30:38 vm0 pengine: [2264]: notice: common_apply_stickiness: p_keystone can fail 999588 more times on vm0 before being forced off
Mar 13 15:30:38 vm0 pengine: [2264]: info: get_failcount: p_keystone has failed INFINITY times on vm1
Mar 13 15:30:38 vm0 pengine: [2264]: WARN: common_apply_stickiness: Forcing p_keystone away from vm1 after 1000000 failures (max=1000000)
Mar 13 15:30:38 vm0 crmd: [2265]: info: te_rsc_command: Initiating action 6: stop p_keystone_stop_0 on vm0 (local)
Mar 13 15:30:38 vm0 crmd: [2265]: debug: cancel_op: Cancelling op 1461 for p_keystone (p_keystone:1461)
Mar 13 15:30:38 vm0 lrmd: [2262]: info: cancel_op: operation monitor[1461] on p_keystone for client 2265, its parameters: CRM_meta_timeout=[30000] os_username=[admin] CRM_meta_name=[monitor] crm_feature_set=[3.0.5] config=[/etc/keystone/keystone.conf] os_tenant_name=[demo] CRM_meta_interval=[30000] os_password=[gkeZe67EBCaF] os_auth_url=[http://192.168.10.103:5000/v2.0/]  cancelled
Mar 13 15:30:38 vm0 crmd: [2265]: debug: cancel_op: Op 1461 for p_keystone (p_keystone:1461): cancelled
Mar 13 15:30:38 vm0 crmd: [2265]: info: do_lrm_rsc_op: Performing key=6:1151:0:cca7f396-8e31-40a7-a2f3-ce95acca4de1 op=p_keystone_stop_0 )
Mar 13 15:30:38 vm0 lrmd: [2262]: debug: on_msg_perform_op: add an operation operation stop[1462] on p_keystone for client 2265, its parameters: crm_feature_set=[3.0.5]  to the operation list.
Mar 13 15:30:38 vm0 lrmd: [2262]: info: rsc:p_keystone stop[1462] (pid 20706)
Mar 13 15:30:38 vm0 crmd: [2265]: info: process_lrm_event: LRM operation p_keystone_monitor_30000 (call=1461, status=1, cib-update=0, confirmed=true) Cancelled
Mar 13 15:30:38 vm0 crmd: [2265]: debug: update_history_cache: Appending monitor op to history for 'p_keystone'
Mar 13 15:30:39 vm0 lrmd: [2262]: info: Managed p_keystone:stop process 20706 exited with return code 0.
Mar 13 15:30:39 vm0 lrmd: [2262]: info: operation stop[1462] on p_keystone for client 2265: pid 20706 exited with return code 0
Mar 13 15:30:39 vm0 crmd: [2265]: debug: create_operation_update: do_update_resource: Updating resouce p_keystone after complete stop op (interval=0)
Mar 13 15:30:39 vm0 crmd: [2265]: info: process_lrm_event: LRM operation p_keystone_stop_0 (call=1462, rc=0, cib-update=3621, confirmed=true) ok
Mar 13 15:30:39 vm0 crmd: [2265]: debug: update_history_cache: Appending stop op to history for 'p_keystone'
Mar 13 15:30:39 vm0 crmd: [2265]: info: match_graph_event: Action p_keystone_stop_0 (6) confirmed on vm0 (rc=0)
Mar 13 15:30:39 vm0 crmd: [2265]: info: te_rsc_command: Initiating action 102: start p_keystone_start_0 on vm0 (local)
Mar 13 15:30:39 vm0 crmd: [2265]: info: do_lrm_rsc_op: Performing key=102:1151:0:cca7f396-8e31-40a7-a2f3-ce95acca4de1 op=p_keystone_start_0 )
Mar 13 15:30:39 vm0 lrmd: [2262]: debug: on_msg_perform_op:2396: copying parameters for rsc p_keystone