From f952101e8ea5a8cebb32ecdde2949e52e6f0c3d0 Mon Sep 17 00:00:00 2001 From: Thales Elero Cervi Date: Wed, 28 Aug 2024 14:14:40 -0300 Subject: [PATCH] Zuul/Tox: Fix stx-virt-pylint node set As per the reported launchpad [1], Zuul recently updated its default nodeset from Ubuntu 22 to 24. Now, we need to set our jobs nodeset to debian-bullsseye to properly execute it. This was causing Zuul errors to any stx/virt change, but was not related to the change content [2]. [1] https://bugs.launchpad.net/starlingx/+bug/2077748 [2] https://zuul.opendev.org/t/openstack/build/9f030173bfaa4bf68e43471df120736a Test Plan: PASS - stx-virt-pylint successfully executed Partial-Bug: 2077748 Change-Id: I10e0b1e6f0d6d8b88914e779e05165150df4d42a Signed-off-by: Thales Elero Cervi --- .zuul.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/.zuul.yaml b/.zuul.yaml index dd73f93..e68d1ff 100644 --- a/.zuul.yaml +++ b/.zuul.yaml @@ -165,6 +165,7 @@ - job: name: stx-virt-pylint parent: tox + nodeset: debian-bullseye required-projects: - starlingx/config vars: