From 1ba0d961a39d8bb73726138fb580bec554c45444 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Tue, 9 Jun 2026 19:24:21 +0000 Subject: [PATCH] test(plausible): pin UPGRADE_BASE_VERSION to 3.0.1+v2.0.0 (newest published) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The harness default base (recipe_versions[-2]) resolves to 3.0.0+v2.0.0 for the open 3.1.0 upgrade PR. That release predates x86_64 support in the clickhouse entrypoint (added 3.0.1): on this amd64 host it downloads clickhouse-backup-linux-x86_64.tar.gz — a deterministic HTTP 404 — and with set -e + a silenced wget the container exits 1 before logging anything, crash-looping until the deploy times out. The base therefore can never converge, regardless of the PR content (the published tag is immutable). This is exactly the case the harness documents for UPGRADE_BASE_VERSION: a PR adding its version ABOVE the newest published tag, where the true predecessor is [-1] (3.0.1+v2.0.0), not [-2]. The upgrade tier then tests the real operator path 3.0.1 -> 3.1.0. Pairs with recipe-maintainers/plausible#3 (its !testme can only go green once this lands). --- tests/plausible/recipe_meta.py | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/tests/plausible/recipe_meta.py b/tests/plausible/recipe_meta.py index 5a0633b..ff77f0a 100644 --- a/tests/plausible/recipe_meta.py +++ b/tests/plausible/recipe_meta.py @@ -20,3 +20,12 @@ EXTRA_ENV = { # 64-char stable value for CI — plausible (Phoenix) requires >= 64 chars "SECRET_KEY_BASE": "ccciplausibletestkeybase64charsexactlyforCIephemeral4567890123", } + +# The upgrade tier defaults its base to recipe_versions[-2]. For the 3.1.0 upgrade PR the +# published tags end [..., 3.0.0+v2.0.0, 3.0.1+v2.0.0], so [-2] picks 3.0.0 — whose clickhouse +# entrypoint has no x86_64 ARCH mapping (added in 3.0.1): on amd64 it wgets the nonexistent +# clickhouse-backup-linux-x86_64.tar.gz (HTTP 404), exits 1 silently (set -e + silenced wget) +# and crash-loops, so the base deploy can NEVER converge on this host. The PR adds its version +# ABOVE the newest published tag — the documented case where the correct base is [-1], the +# newest published version. Pin it. +UPGRADE_BASE_VERSION = "3.0.1+v2.0.0"