Repository navigation
Commit bf54baf
committed
ci(fresh-install): the tumbleweed leg refreshes before it installs and stops when the refresh fails
The tumbleweed leg ran `zypper -n install ...` alone. That install refreshes
the repositories itself, and when the refresh fails it continues on stale or
empty metadata, so the leg went red with
Some of the repositories have not been refreshed because of an error.
No provider of 'binutils' found.
The second line is the one a reader acts on, and it names a package rather
than the repository that could not be read.
The leg's setup now runs `zypper -n --gpg-auto-import-keys refresh` as its
own command, retries it once after 15 seconds, and installs only after it
succeeds. A refresh that fails twice ends the step with zypper's own refresh
error and status. --gpg-auto-import-keys accepts a repository's new signing
key, which `-n` alone rejects on a rolling image.
Measured in opensuse/tumbleweed:latest (aarch64) under `sh -e`, as a
container step runs: with a repository at an unreachable URL added, both
refreshes fail, the install never starts and the step exits 4 after
"Some of the repositories have not been refreshed"; without it the refresh
succeeds and the install proceeds.
Closes #523.1 parent 304487b commit bf54baf
1 file changed
Lines changed: 11 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
279 | 279 | | |
280 | 280 | | |
281 | 281 | | |
| 282 | + | |
| 283 | + | |
| 284 | + | |
| 285 | + | |
| 286 | + | |
| 287 | + | |
| 288 | + | |
282 | 289 | | |
283 | 290 | | |
284 | | - | |
| 291 | + | |
| 292 | + | |
| 293 | + | |
| 294 | + | |
285 | 295 | | |
286 | 296 | | |
287 | 297 | | |
| |||
0 commit comments