Damien Ciabrini 015211b188 HA: increase resource default op timeout for podman bundles ... Pacemaker currently relies on a single, system-wide timeout for every operation run on containers, set by default to 20s. With podman's reliance on disk, the default timeout can be reached under high disk IO (e.g. during container-puppet or when paunch restart containers from step 4). This causes unneeded resource restart in pacemaker and can even trigger fencing if stop operations time out. Raise the default to a safer value of 120s when using podman, and make that default timeout configurable via a new Heat parameter PacemakerBundleOperationTimeout. Closes-Bug: #1834325 Change-Id: Ie45a56b8dab1272798440110ad96b6ee11fcf26b (cherry picked from commit 744da29ba7) (cherry picked from commit add09e8634)		2020-01-27 12:47:17 +00:00
..
extraconfig	Handle upper and lower case system uuids	2019-02-19 12:58:54 -07:00
manifests	Reinstate common overcloud manifest for all roles	2018-01-11 18:42:45 +00:00
services	HA: increase resource default op timeout for podman bundles	2020-01-27 12:47:17 +00:00
all-nodes-config.j2.yaml	No cloud_name_$NET_NAME for disabled networks	2019-08-30 00:15:54 +02:00
deploy-artifacts.sh	Correct file modes for rpmlint failures	2018-12-14 13:21:28 -07:00
deploy-artifacts.yaml	Change template names to rocky	2018-05-09 08:28:42 +02:00
role.role.j2.yaml	Derives NovaPCIPassthrough per SR-IOV node	2019-10-25 06:50:54 +05:30