Fix bug 1653 to update osm_health increasing time_for_failure 54/11154/2 v10.0.2
authorgarciadeblas <gerardo.garciadeblas@telefonica.com>
Tue, 7 Sep 2021 16:58:35 +0000 (18:58 +0200)
committergarciadeblas <gerardo.garciadeblas@telefonica.com>
Mon, 13 Sep 2021 08:37:50 +0000 (10:37 +0200)
Recent tests showed that the 5 minutes assigned to the time for checking
failures in pods were not enough. This change increases the time to 7
minutes, which will be enough even for the long tail cases.

Change-Id: Ic9c721811a187292c1da6f421f2ed4311b7f4622
Signed-off-by: garciadeblas <gerardo.garciadeblas@telefonica.com>
installers/osm_health.sh

index 5ee3d78..6c314fb 100755 (executable)
@@ -17,7 +17,7 @@
 # Default values
 sampling_period=5       # seconds
 time_for_readiness=2    # minutes ready
-time_for_failure=5      # minutes broken
+time_for_failure=7      # minutes broken
 KUBERNETES=             # By default, assumes Docker Swarm installation
 STACK_NAME=osm          # By default, "osm"