Pacemaker neutron agent scripts start/stop/migration will fail if management vip moved recently

{"build_id": "2014-03-04_12-31-13", "mirantis": "yes", "build_number": "112", "nailgun_sha": "d98b61e073d32c45c98099a11ff263a68b7ba205", "ostf_sha": "dc54d99ddff2f497b131ad1a42362515f2a61afa", "fuelmain_sha": "16637e2ea0ae6fe9a773aceb9d76c6e3a75f6c3b", "astute_sha": "f15f5615249c59c826ea05d26707f062c88db32a", "release": "4.1", "fuellib_sha": "15a55ccff0f59929b32d087679d19e896bde8e0d"}

Steps to reproduce:
1 - Deploy Ubuntu HA (Cinder LVM backend, Swift glance backend, Neutron with GRE segmentation) 3 computes - 1 controller - 1 storage
2 - Log into first controller and run crm_resource -r vip__management_old --move --node node-3 (NOTE: replace node-3 where it is the nonprimary controller)
3 - Wait ~60s for keystone and other services to recover
4 - Run neutron agent-list

Results:

# neutron agent-list
+--------------------------------------+--------------------+--------+-------+----------------+
| id | agent_type | host | alive | admin_state_up |
+--------------------------------------+--------------------+--------+-------+----------------+
| 09699e60-aa51-4a66-bf0f-bb8eeab49da5 | L3 agent | node-3 | xxx | True |
| 12236192-8980-4068-8ed8-adc94eb1f681 | Open vSwitch agent | node-1 | :-) | True |
| 2c0ec06d-087c-4e45-b066-403ce6a97f51 | Open vSwitch agent | node-2 | :-) | True |
| ad4c9181-6a26-4b4c-be22-214c3df2514e | DHCP agent | node-1 | xxx | True |
| bd893993-5768-4182-ac4a-ff71e7905a64 | Open vSwitch agent | node-3 | :-) | True |
| f7451cfd-600a-444b-8d36-2af7b21714c3 | Open vSwitch agent | node-4 | :-) | True |

# crm resource show | egrep 'l3|dhcp'
 p_neutron-dhcp-agent (ocf::mirantis:neutron-agent-dhcp): Started (unmanaged) FAILED
 p_neutron-l3-agent (ocf::mirantis:neutron-agent-l3): Started (unmanaged) FAILED

From l3 agent logs:
p_neutron-l3-agent_start_0:4166:stderr [ Traceback (most recent call last): ]
p_neutron-l3-agent_start_0:4166:stderr [ File "/usr/bin/q-agent-cleanup.py", line 525, in <module> ]
p_neutron-l3-agent_start_0:4166:stderr [ cleaner = NeutronCleaner(get_authconfig(args.authconf), options=vars(args), log=LOG) ]
p_neutron-l3-agent_start_0:4166:stderr [ File "/usr/bin/q-agent-cleanup.py", line 106, in __init__ ]
p_neutron-l3-agent_start_0:4166:stderr [ raise e ]
p_neutron-l3-agent_start_0:4166:stderr [ keystoneclient.apiclient.exceptions.AuthorizationFailure: Authorization Failed: An unexpected erro
(2013, "Lost connection to MySQL server at 'reading initial communication packet', system error: 0") None None (HTTP 500) ]
p_neutron-dhcp-agent_start_0:4153:stderr [ Traceback (most recent call last): ]
p_neutron-dhcp-agent_start_0:4153:stderr [ File "/usr/bin/q-agent-cleanup.py", line 525, in <module> ]
p_neutron-dhcp-agent_start_0:4153:stderr [ cleaner = NeutronCleaner(get_authconfig(args.authconf), options=vars(args), log=LOG) ]
p_neutron-dhcp-agent_start_0:4153:stderr [ File "/usr/bin/q-agent-cleanup.py", line 106, in __init__ ]
p_neutron-dhcp-agent_start_0:4153:stderr [ raise e ]

We should tune OCF scripts and/or q-agent-cleanup.py to be more tolerant of keystone being unavailable for up to 2 minutes.