From 828ec8986ee4ca72254bf34423debaf81e7e4857 Mon Sep 17 00:00:00 2001 From: Sreenath Bodagala Date: Tue, 11 Jul 2023 19:07:21 +0000 Subject: [PATCH] - Add an explanation for the number of recoveries that happen during an upgrade. --- e2e/test_operator_ha_upgrades/operator_ha_upgrade_test.go | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/e2e/test_operator_ha_upgrades/operator_ha_upgrade_test.go b/e2e/test_operator_ha_upgrades/operator_ha_upgrade_test.go index 403ce5775..9a8eed6a6 100644 --- a/e2e/test_operator_ha_upgrades/operator_ha_upgrade_test.go +++ b/e2e/test_operator_ha_upgrades/operator_ha_upgrade_test.go @@ -262,9 +262,10 @@ var _ = Describe("Operator HA Upgrades", Label("e2e", "pr"), func() { // Verify that the cluster generation number didn't increase by more // than 80 (in an ideal case the number of recoveries that should happen - // during an upgrade is 9, but in reality that number could be higher - // because different server processes may get bounced at different times). - // See: https://github.com/FoundationDB/fdb-kubernetes-operator/issues/1607 + // during an upgrade, because of bouncing of server processes, is 9, but + // in reality that number could be higher because different server processes + // may get bounced at different times and also because of cluster controller + // change, which happens a number of times, during an upgrade). Expect(finalGeneration).To(BeNumerically("<=", initialGeneration+80)) }, EntryDescription("Upgrade from %[1]s to %[2]s"),