From 34b2a772947597e26543a4cdd8dcd8876633a113 Mon Sep 17 00:00:00 2001 From: Alexander Kukushkin Date: Fri, 31 Jan 2025 16:45:26 +0100 Subject: [PATCH] Fix race condition in priority sync behave tests (#3263) don't try patching /config key before leader managed to create it. --- features/priority_sync.feature | 2 ++ 1 file changed, 2 insertions(+) diff --git a/features/priority_sync.feature b/features/priority_sync.feature index a84fe7de..f1de3c1d 100644 --- a/features/priority_sync.feature +++ b/features/priority_sync.feature @@ -3,6 +3,8 @@ Feature: synchronous replicas priority Scenario: check replica with sync_priority=0 does not become a synchronous replica Given I start postgres-0 + Then postgres-0 is a leader after 10 seconds + And there is a non empty initialize key in DCS after 15 seconds When I issue a PATCH request to http://127.0.0.1:8008/config with {"ttl": 20, "synchronous_mode": true} Then I receive a response code 200 When I configure and start postgres-1 with a tag sync_priority 0