Bug 1295830
Summary: | Increase timeout defaults for pacemaker | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Michele Baldessari <michele> | |
Component: | openstack-tripleo-heat-templates | Assignee: | Marios Andreou <mandreou> | |
Status: | CLOSED ERRATA | QA Contact: | Giulio Fidente <gfidente> | |
Severity: | high | Docs Contact: | ||
Priority: | urgent | |||
Version: | 8.0 (Liberty) | CC: | dmacpher, gfidente, hbrock, kbasil, mburns, mcornea, rhel-osp-director-maint | |
Target Milestone: | ga | Keywords: | Triaged | |
Target Release: | 8.0 (Liberty) | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | openstack-tripleo-heat-templates-0.8.8-1.el7ost | Doc Type: | Bug Fix | |
Doc Text: |
Pacemaker used a 100s timeout for service resources. However, a systemd timeout requires an additional timeout period after the initial timeout to accommodate for a SIGTERM and then a SIGKILL. This fix increases the Pacemaker timeout to 200s to accommodate two full systemd timeout periods. Now the timeout period is enough for systemd to perform a SIGTERM and then a SIGKILL.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1295835 (view as bug list) | Environment: | ||
Last Closed: | 2016-04-07 21:44:39 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1295835 |
Description
Michele Baldessari
2016-01-05 15:03:47 UTC
Reassigning to Marios since he's already working on it. In openstack-tripleo-heat-templates-0.8.12-2.el7ost.noarch.rpm all the systemd resources have a start and stop timeout set to 200s (except mongodb which uses an even higher start timeout, 370s). Note that non-systemd resources (like galera, redis, rabbitmq or IPs) will use shorter timeouts, as defined in the respective resource agents. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0604.html |