Drop --retry-all-errors so the OL8 psmdb image builds again - #1183
Merged
Conversation
This was referenced Aug 14, 2026
curl gained --retry-all-errors in 7.71.0; OL8 ships 7.61.1, so the flag added in #1171 aborts the build at the first curl with 'option --retry-all-errors: is unknown'. All 7 OL8 jobs of the GSSAPI nightly failed in setup while every OL9 job (curl 7.76.1) passed. --retry 5 --retry-delay 5 both predate 7.61.1 and stay. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Claude <noreply@anthropic.com>
travagliad
force-pushed
the
claude/elegant-cerf-ylxlu5
branch
from
August 14, 2026 09:53
a3fec13 to
bd1b2b5
Compare
travagliad
approved these changes
Aug 14, 2026
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
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.
Failures fixed (investigator)
PSMDB GSSAPI E2E Tests Matrix, scheduled onmainqa-integration/pmm_psmdb-pbm_setup/Dockerfile(image build,OL_VERSION=8) — setup step, all 7 OL8 jobs:OL8 PSMDB E2E tests / e2e tests: @rtaOL8 PSMDB E2E tests / e2e tests: @pmm-psmdb-replica-integrationOL8 PSMDB E2E tests / e2e tests: @mongodb-exporterOL8 PSMDB E2E tests / e2e tests: @bm-mongoOL8 CLI / Integration / PSMDB Replica 6.xOL8 CLI / Integration / PSMDB Replica 7.xOL8 CLI / Integration / PSMDB Replica 8.xWhat failed
Every OL8 job died in
Run Setup for E2E Tests; no test ever ran. Every OL9counterpart passed. The split is exactly on
OL_VERSION:0.143s into the
RUN— argument parsing, not a network problem.Root cause
--retry-all-errorswas added to bothcurlcalls in this Dockerfile byb071e8d (#1171, merged Aug 13
13:24 UTC). This run (Aug 14 02:49 UTC) is the first scheduled one after that
merge.
The flag is newer than the curl OL8 ships:
--retry-all-errors(needs 7.71.0)oraclelinux:8oraclelinux:9Sources: curl's own
retry-all-errors.mdsays
Added: 7.71.0; OL8 baseosships only
curl-7.61.1-*.el8.#1171 was only ever exercised on OL9, so the incompatibility reached
mainunnoticed.The fix
Remove the one flag that OL8 rejects.
--retry 5and--retry-delay 5bothlong predate 7.61.1 and stay, so the retry behaviour #1171 wanted is kept
wherever curl supports it.
What #1171 actually fixed — the
&&chain, so a failed download fails thebuild instead of shipping a broken image — is untouched and still on
main.That was the substance of #1171;
--retry-all-errorswas an add-on.The failure #1171 was actually reacting to stays covered. Its CI log shows
curl: (22) The requested URL returned error: 503, and because these commandsuse
-f, a 503 lands in curl's own retry path (CURLE_HTTP_RETURNED_ERROR→case 503→ retry — present in 7.61.1'ssrc/tool_operate.c). So--retry 5 --retry-delay 5still rides out the transient 5xx that motivated the flag.What does narrow, stated rather than papered over: without
--retry-all-errorscurl no longer retries connect-refused (error 7) or mid-transfer death
(error 56). Neither is #1171's CI failure — error 7 is what its verification
simulated (
--add-host github.com:127.0.0.1, which is why an OL8-incompatibleflag passed review), and error 56 comes from #1172's incident. If reviewers want
connect-refused back,
--retry-connrefusedis in curl 7.61.1's option table(added 7.52.0) and is safe on OL8. Error 56 would need a shell retry loop —
more machinery in an already dense
RUNthan this warrants unless it recurs.Verified
--retry-all-errorsremains anywhere in the repo.against curl-7.61.1's own
src/tool_getparam.coption table, which listsretry,retry-connrefused,retry-delay,retry-max-timeand noretry-all-errors.(
-o /tmp/...spacing intact,\still the final byte); the wholeRUN,continuations joined, passes
bash -nandbash --posix -n.What this does not prove
I could not build the OL8 image. Provisioning a repro VM got as far as
creating it, but the relay's
/linode/provision-resultendpoint was blocked bythis session's permission classifier, so its credentials were unreachable; the
VM was destroyed immediately and there is no Docker daemon in the agent
sandbox. So the evidence is the CI log plus primary-source version facts —
not a green
docker build --build-arg OL_VERSION=8.That build is worth running before merge, or letting the next scheduled
PSMDB GSSAPI E2E Tests Matrixconfirm.Also worth knowing
Open PR #1172 is a near-duplicate
of the already-merged #1171 on this same file and also adds
--retry-all-errors— merging it as-is would re-break OL8. It should beclosed or rebased onto this change.
Generated by Claude Code