rabbitmq resource needs increase start/stop timeouts

Bug #1633455 reported by Michele Baldessari
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Unassigned

Bug Description

In all our releases liberty/mitaka/newton we have the following timeouts set in the pacemaker resources for rabbitmq and redis:
- rabbitmq
start interval=0s timeout=100 (rabbitmq-start-interval-0s)
stop interval=0s timeout=90 (rabbitmq-stop-interval-0s)

- redis
start interval=0s timeout=120 (redis-start-interval-0s)
stop interval=0s timeout=120 (redis-stop-interval-0s)

It makes sense to increase these since we have seen especially rabbitmq fail to stop within 90s which breaks "openstack stack update" because we do call a "pcs resource rabbitmq restart" there.

Steven Hardy (shardy)
Changed in tripleo:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Emilien Macchi (emilienm) wrote :
Changed in tripleo:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.