Bug 1123314
| Summary: | Rubygem-staypuft: HA: Relax the openstack-heat-engine: op monitor interval to 60 seconds. | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Leonid Natapov <lnatapov> |
| Component: | openstack-foreman-installer | Assignee: | Crag Wolfe <cwolfe> |
| Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0 (RHEL 7) | CC: | cwolfe, dnavale, fdinitto, jguiditt, mburns, morazi, rhos-maint, yeylon |
| Target Milestone: | ga | ||
| Target Release: | Installer | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-foreman-installer-2.0.19-1.el6ost | Doc Type: | Bug Fix |
| Doc Text: |
Previously, openstack-heat-engine monitor interval parameter value was set too low for Galera (MariaDB) for Pacemaker to identify that Orchestration service was running. This caused the Orchestration service to restart as random intervals.
With this bug fix, the monitor interval has been increased to 60s and as a result, Orchestration service is not unnecessarily restarted by Pacemaker.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-08-21 18:06:25 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: | |||
|
Description
Leonid Natapov
2014-07-25 09:51:00 UTC
This bug causes heat service to go up/down at random interval. I consider this a blocker. Patch posted: https://github.com/redhat-openstack/astapor/pull/338 It looks like the heat how-to should be updated as well. (In reply to Crag Wolfe from comment #3) > It looks like the heat how-to should be updated as well. I don't understand the point here. The heat how-to uses the default monitor op of 60 seconds by not specifying any value. http://rhel-ha.etherpad.corp.redhat.com/RHOS-RHEL-HA-how-to-mrgcloud-rhos5-on-rhel7-heat line 61: pcs resource create heat-engine systemd:openstack-heat-engine op monitor start-delay=10s default is 60. My mistake, I did not realize the 60s was global across all services. Should we open another bug to change the interval to 60s for all services (right now the default is 30s as deployed by puppet)? (In reply to Crag Wolfe from comment #6) > My mistake, I did not realize the 60s was global across all services. > Should we open another bug to change the interval to 60s for all services > (right now the default is 30s as deployed by puppet)? It's a bit tricky here. I think default should be 60 and match pacemaker default but we probably want the ability to configure that value. Now, I experienced those timeout because hw was "questionable" and slow. Customers might not experience the same and perhaps want faster failure detection. Merged openstack-foreman-installer-2.0.20-1.el6ost [root@mac047d7b627d5a haproxy]# pcs resource show openstack-heat-engine Resource: openstack-heat-engine (class=systemd type=openstack-heat-engine) Attributes: start-delay=10s Operations: monitor interval=60s (openstack-heat-engine-monitor-interval-60s) 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. http://rhn.redhat.com/errata/RHBA-2014-1090.html |