From 6f5db247ba0dbf76b9c1c8dafa23b397faeed6d9 Mon Sep 17 00:00:00 2001 From: Clark Boylan Date: Mon, 31 Mar 2025 14:41:01 -0700 Subject: [PATCH] Switch nox job default back to Jammy When I was trying to get Zuul to test against MariaDB by default I switched the base test node to bookworm so that py311 and MariaDB 10.11 would be used together. The reason for this is it seemed like maybe MariaDB 10.6 on Jammy was buggy and causing our connection errors. Since then we've discovered that 10.11 and 10.6 share the same underlying bug which we worked around via not flushing privileges. Switch these tests back to Jammy as this will simplify the process of dogfooding zuul-launcher (one less image to worry about). Change-Id: I1ed4252617e5570522838e87dca4d8caefb8849e --- .zuul.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.zuul.yaml b/.zuul.yaml index 66fb31c7d8..cef105d263 100644 --- a/.zuul.yaml +++ b/.zuul.yaml @@ -59,7 +59,7 @@ description: | Zuul unit tests with ZooKeeper running parent: nox - nodeset: debian-bookworm + nodeset: ubuntu-jammy pre-run: playbooks/zuul-nox/pre.yaml post-run: playbooks/zuul-nox/post-system-logs.yaml vars: @@ -79,7 +79,7 @@ - job: name: zuul-nox-remote parent: nox - nodeset: debian-bookworm + nodeset: ubuntu-jammy timeout: 2700 # 45 minutes pre-run: playbooks/zuul-nox/pre.yaml post-run: playbooks/zuul-nox/post-system-logs.yaml