lrmd ignores timeouts for start|stop|monitor when managing upstart jobs
Bug #939327 reported by
Ante Karamatić
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cluster-glue (Ubuntu) |
Fix Released
|
Undecided
|
Ante Karamatić | ||
Bug Description
If the primitive has a timeout set to 26 or higher, lrmd will declare start|stop|monitor as failed after 25 seconds, ignoring the configured timeout. Reason for this is default dbus timeout, which is set to 25 seconds.
There's a patch accepted by upstream: http://
| Changed in cluster-glue (Ubuntu): | |
| assignee: | nobody → Ante Karamatić (ivoks) |
| status: | New → Confirmed |
Revision history for this message
| Rafael David Tinoco (rafaeldtinoco) wrote | #1 |
| Changed in cluster-glue (Ubuntu): | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
This has been upstreamed long time ago:
commit faa022c14609d74
Author: Ante Karamatić <email address hidden>
Date: Fri Feb 17 05:25:46 2012
Medium: LRM: lrmd: use the resource timeout as an override to the default dbus timeout for upstart RA
and this bug can be closed as Fix Released.