Repository navigation
fix(docker): disable an unreachable Tumbleweed Update repo instead of failing the rung - #174
Merged
Merged
Conversation
…e rung After #169 merged, the opensuse tumbleweed rung went red without compiling anything. The openSUSE-Tumbleweed-Update repo timed out ("Curl error (28)") on every one of the four refresh retries. The plain install then failed, and the `zypper dup` fallback refuses outright to run while any enabled repo failed to refresh. When the retried refresh still fails, that one repo is now disabled. It only carries rare urgent patches; Tumbleweed itself ships through Oss. A plain install can live with a stale repo, and dup can now run. Other repos are untouched: one that keeps failing still fails the build.
modifyrepo matches aliases; openSUSE-Tumbleweed-Update is only the display name, so the previous line disabled nothing and '|| true' hid the error.
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
2 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.
Fixes the red
opensuse tumbleweedrung on develop 87ec34d, run 39064261297, which went green only after a rerun.Root cause: the openSUSE mirror timed out for the Update repo (alias
repo-update, display nameopenSUSE-Tumbleweed-Update):Curl error (28). The install fallback runszypper dup, which refuses to run while any enabled repo failed to refresh.Fix: when the refresh still fails after the retries,
zypper modifyrepo --disable repo-update. There's no|| true, so an image that renames the alias fails loudly instead of silently disabling nothing. The first commit used the display name, whichmodifyrepodoesn't match; the probe below caught that.Proof (throwaway workflow on
exp/opensuse-update-down, now deleted; run 39074217434). Both variants pointrepo-update's baseurl athttp://invalid.invalid/and force azypper dup --dry-run. Guards abort unless the sabotage line ran and zypper reported "Failed to retrieve new repository metadata".modifyrepo --disable repo-updateranTwo earlier probe runs were invalid: one used
modifyrepo --url(no such flag), and one had a guard that couldn't abort underset +e. Their results were discarded.🤖 Generated with Claude Code