pacemaker: increase timeouts for rabbitmq and redis
authorEmilien Macchi <emilien@redhat.com>
Wed, 12 Oct 2016 16:32:18 +0000 (12:32 -0400)
committerEmilien Macchi <emilien@redhat.com>
Wed, 12 Oct 2016 16:32:18 +0000 (12:32 -0400)
commit12910de9230ab5e04b0f8a78cc6245186f4cea34
tree0f72f57689a7f76dcf085da45aaf6c2379d6154c
parent8a4d7ae04f773385d1a6677ad635859d753337ab
pacemaker: increase timeouts for rabbitmq and redis

When we observe the 'stop timeout' values of pacemaker resources:
rabbitmq and redis, they are set to 90s. But for all other services, it
is set to 200s.
The overcloud deployment sometimes fails due to this with the error:
Error: Could not complete shutdown of rabbitmq-clone, 1 resources
remaining
Error performing operation: Timer expired

This patch updates the timeout for Redis and RabbitMQ to avoid this
error.

Change-Id: I8a3b3951a896ee3e8e5e09778e8ea4717e76a1b4
manifests/profile/pacemaker/database/redis.pp
manifests/profile/pacemaker/rabbitmq.pp