Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cirrus: aarch64: 404 in clone #18040

Closed
edsantiago opened this issue Apr 4, 2023 · 3 comments · Fixed by #18069
Closed

Cirrus: aarch64: 404 in clone #18040

edsantiago opened this issue Apr 4, 2023 · 3 comments · Fixed by #18069
Assignees
Labels
flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@edsantiago
Copy link
Member

Occasionally the CI clone job will 404:

cd /tmp
echo "$ARTCURL/build_aarch64/repo/repo.tbz"
curl --retry 5 --retry-delay 8 --fail --location -O --url https://api.cirrus-ci.com/v1/artifact/build/5921399689183232/build_aarch64/repo/repo.tbz
time $ARTCURL/build_aarch64/repo/repo.tbz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0    70    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404

Seems to be aarch64 only. (Other arches also have clone flakes, but I haven't seen this 404).

sys remote fedora-37-aarch64 root host boltdb: unknown failure

sys podman fedora-37-aarch64 root host boltdb: unknown failure

@edsantiago edsantiago added flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. labels Apr 4, 2023
@cevich
Copy link
Member

cevich commented Apr 4, 2023

Thanks @edsantiago I'll take a look into it.

@cevich
Copy link
Member

cevich commented Apr 5, 2023

Examining a recent occurence, I see the aarch64 task isn't depending on the build_aarch64 task (where the archive is being downloaded from). Looking at that task I see there was a failure in pre-build: dial tcp: lookup cdn03.quay.io: no such host.

I haven't examined the other reported incidents yet, but the missing dependency is definitely a problem, and certainly one that will cause a 404. Opened #18069

@cevich
Copy link
Member

cevich commented Apr 5, 2023

Confirmed: Looked at a few more failure logs. The build_aarch64 tasks are failing in pre-build because of the damn dumb infuriating systemd-resolved + quay DNS problem. Since the system-test dependencies are wrong, the cirrus artifact-download API will not work right, leading to a 404. So #18069 will definitely fix this.

cevich added a commit to cevich/podman that referenced this issue Apr 5, 2023
Fixes: containers#18040

If the `build_aarch64` task happens to fail for any reason, it will
cause the `curl` command in the `clone_script` for the aarch64 system
test tasks to throw a 404.  This is because the
`local_system_test_aarch64_task` depends on `build` not `build_aarch64`.
As discovered in another issue long ago, the Cirrus API depends on doing
some dependency-resolution magic to function properly.  Fix this by
correcting the dependencies.

Signed-off-by: Chris Evich <[email protected]>
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Aug 28, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants