Public bug reported: 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://hg.linux- ha.org/glue/rev/6f8d63c39207 ** Affects: cluster-glue (Ubuntu) Importance: Undecided Assignee: Ante Karamatić (ivoks) Status: Confirmed ** Changed in: cluster-glue (Ubuntu) Assignee: (unassigned) => Ante Karamatić (ivoks) ** Changed in: cluster-glue (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to cluster-glue in Ubuntu. https://bugs.launchpad.net/bugs/939327 Title: lrmd ignores timeouts for start|stop|monitor when managing upstart jobs Status in “cluster-glue” package in Ubuntu: Confirmed 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://hg.linux- ha.org/glue/rev/6f8d63c39207 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/939327/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
