ci: drop debian-11 (EOL) from CI matrix - #70238
Open
twangboy wants to merge 1 commit into
Open
Conversation
Debian 11 (bullseye) reached the end of its LTS window on 2026-08-31 (https://www.debian.org/releases/bullseye/). Its security suite is now frozen (the Release file's own Date field is stuck at that exact moment) and packages are becoming unreliable to fetch - this has been repeatedly breaking salt-ci-containers' testing:debian-11 image build, which in turn blocks publication of every other image in the same run. Salt's own published support policy already excludes this case: 'Debian stable, oldstable, and oldoldstable (if it is not EOL) versions.' Debian 11 is oldoldstable and is now EOL, so it falls outside Salt's own supported list - the 'Full' entry in the supported-OS table just hasn't caught up to that yet. debian-13 is already enabled (x86_64 in the regular test matrix, arm64 in the pkg matrix), so Debian keeps CI coverage without further changes. Follows the same slug-swap precedent as 972e0d5 (Fedora 40 -> 43).
This was referenced Sep 4, 2026
3 tasks
dwoz
pushed a commit
that referenced
this pull request
Sep 10, 2026
CreateService for salt-minion can race the SCM's async cleanup after a prior uninstall's SimpleSC::RemoveService, since the SCM doesn't purge the service registry key until every handle is closed. The existing 15s wait / 20s CreateService retry budget was too tight: PR #70238 stress run 33911838747 (iteration 88) showed this window climbing past 35s under load before exhausting the retries and aborting. - Raise the install-side pending-deletion wait and the uninstall-side post-removal wait from 15s to 60s (30->120 polls at 500ms) in Salt-Minion-Setup.nsi. - Raise the CreateService retry loop from 10 to 20 attempts (2s apart, 40s total). - Raise SCM_WAIT_SECS in conftest.py's clean_env() from 15s to 60s to match. - Log elapsed wait time on the success path (not just on timeout) in all three wait loops, so future stress-test logs show the SCM latency trend across iterations instead of only surfacing it once a run blows the budget and fails.
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
1 participant
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.
Debian 11 (bullseye) reached the end of its LTS window on 2026-08-31 (https://www.debian.org/releases/bullseye/). Its security suite is now frozen (the
Releasefile's ownDatefield is stuck at that exact moment) and packages are becoming unreliable to fetch - this has been repeatedly breakingsalt-ci-containers'testing:debian-11image build, which in turn blocks publication of every other image in the same run (the downstreammerge/publish job needs everybuildmatrix entry to succeed, regardless offail-fast: false).Salt's own published support policy already excludes this case: "Debian stable, oldstable, and oldoldstable (if it is not EOL) versions." Debian 11 is
oldoldstableand is now EOL, so it's outside Salt's own supported list - the "Full" entry in the supported-OS table just hasn't caught up to that yet.debian-13is already enabled incicd/shared-gh-workflows-context.yml(x86_64 in the regular test matrix, arm64 in the pkg matrix), so Debian keeps CI coverage without further changes needed. Follows the same slug-swap precedent as972e0d5(Fedora 40 -> 43).Companion PR in
salt-bootstrap: saltstack/salt-bootstrap#2131