zuul: move current lane to OpenStack 2025.1#2902
Merged
Merged
Conversation
The "current" deploy and update lanes still targeted OpenStack 2024.2, which is now a full release behind stable: OSISM 10.0.0 ships 2025.1. Keeping a lane on the end-of-life 2024.2 release no longer reflects what "current" is meant to mean and wastes a nightly slot. Move both current lanes that carried 2024.2 to 2025.1: testbed-deploy-current-in-a-nutshell (the explicit override is kept rather than dropped, to insulate the lane against future default drift) and testbed-update-stable-current (openstack_version_next). Nothing now exercises the EOL 2024.2 release. First landed step of rolling the current/next lanes forward (#2900); the next lane bump to 2026.1 is blocked on 2026.1 support and follows separately. Assisted-by: Claude:claude-opus-4-8 Signed-off-by: Roger Luethi <luethi@osism.tech>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Move both
currenttestbed lanes from OpenStack2024.2to2025.1:testbed-deploy-current-in-a-nutshell-*openstack_version: "2024.2" → "2025.1"(explicit override kept, to insulate the lane against future default drift)
testbed-update-stable-current-ubuntu-24.04openstack_version_next: "2024.2" → "2025.1"Why
currentis meant to track the OpenStack release thelatestdev line ships.After OSISM
10.0.0shipped2025.1(#2857), thecurrentlanes were left on2024.2— now a full release behindstable.2024.2is end-of-life, sothose nightly slots were testing an obsolete release. Nothing exercises 2024.2
after this change.
Both values are actually consumed: the deploy value flows into terraform on a
latestmanager, and the update value hits theMANAGER_VERSION == latestbranch in
upgrade-manager.sh(soset-openstack-version.shapplies it).Scope
This is the first step of #2900. The
nextlane bump to2026.1is blocked on 2026.1 support and follows separately. A previously considered
step that bumped the
openstack_versiondefault inconfiguration.ymlwasdropped as a no-op (the value is shadowed in CI and overwritten on documented
installs by
terraform/Makefile); see #2900 for details.Test
zuul/zuul-additionallabels to run the affectedcurrentlanes against2025.1.
Refs: #2900