From e513f7f12777f5902e534a44bebd6899ee20ca49 Mon Sep 17 00:00:00 2001 From: Alexander Kukushkin Date: Tue, 17 Oct 2023 11:27:41 +0200 Subject: [PATCH] Attempt to reduce flakiness for recovery behave test on K8s (#2917) wait until Postgres is properly started after the first crash before changing `primary_start_timeout` and killing it once again. --- features/recovery.feature | 2 ++ 1 file changed, 2 insertions(+) diff --git a/features/recovery.feature b/features/recovery.feature index 809f7fb9..7839e26f 100644 --- a/features/recovery.feature +++ b/features/recovery.feature @@ -14,6 +14,8 @@ Feature: recovery Then I receive a response code 200 And I receive a response role master And I receive a response timeline 1 + And "members/postgres0" key in DCS has state=running after 12 seconds + And replication works from postgres0 to postgres1 after 15 seconds Scenario: check immediate failover when master_start_timeout=0 Given I issue a PATCH request to http://127.0.0.1:8008/config with {"master_start_timeout": 0}