openstack
/
tripleo-ipsec
Code Issues Proposed changes

Add order constraint for stop operation in resource agent 

We already have an order constraint for the start operation, apparently
we need another one for the stop operation too, as this assures that the
VIP is stopped before the tunnel is put down.

Change-Id: Ica9c2e9c0c2eb24b0f174d30a0d6af1e090768f4
Closes-Bug: #1751265
This commit is contained in:
Juan Antonio Osorio Robles 2018-02-23 15:02:38 +02:00
parent e3bdcc16fc
commit 61eac5e734
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
tasks/resource-agent.yml
View File

@ -33,8 +33,13 @@
when:
- resource_agent.changed or found_resource_agent|failed
- name: Add ordering rule with VIP ( {{ resource_agent_name }} )
command: pcs constraint order start ip-{{ specific_vip }} then {{ resource_agent_name }}
- name: Add ordering rule with VIP ( {{ resource_agent_name }} ) for start operation
command: pcs constraint order start ip-{{ specific_vip }} then start {{ resource_agent_name }} symmetrical=false
when:
- resource_agent.changed or found_resource_agent|failed
- name: Add ordering rule with VIP ( {{ resource_agent_name }} ) for stop operation
command: pcs constraint order stop ip-{{ specific_vip }} then stop {{ resource_agent_name }} symmetrical=false
when:
- resource_agent.changed or found_resource_agent|failed