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

sporadic checksum mismatch #3546

Closed
RoyalOughtness opened this issue Dec 4, 2024 · 9 comments
Closed

sporadic checksum mismatch #3546

RoyalOughtness opened this issue Dec 4, 2024 · 9 comments

Comments

@RoyalOughtness
Copy link

Seeing this after our recent build:

error: Downloading from 'copr:copr.fedorainfracloud.org:secureblue:hardened-chromium': Cannot download 08340627-hardened-chromium/hardened-chromium-common-131.0.6778.108-1.x86_64.rpm: All mirrors were tried; Last error: Downloading successful, but checksum doesn't match. Calculated: 4359c2f3b2ba8070ee4bd7aaaf7eb9a5fffa42f3292573b219e68e54679e20f3(sha256)  Expected: 8ffd6a52379417592935511c08108fbfa0e59a06c995866eda1c17ba5b51545b(sha256) 

Only happens sometimes, a retry or two fixes it. Maybe one of the copr data nodes has a corrupt package?

@praiskup
Copy link
Member

praiskup commented Dec 5, 2024

Thank you for the report.

I believe you were hitting yesterday's outage problems (we had two 15-minute slots with non-working repositories)
https://pagure.io/fedora-infrastructure/issue/12316

Maybe one of the copr data nodes has a corrupt package?

There's just one server, distributed via Amazon CloudFront CDN.

@praiskup praiskup closed this as completed Dec 5, 2024
@RoyalOughtness
Copy link
Author

@praiskup

Amazon CloudFront CDN

Potentially one of the CDN nodes has a corrupt artifact?

This was last seen 10 minutes ago, so it wasn't resolved.

@RoyalOughtness
Copy link
Author

And it's still only seen sporadically. Also, using a VPN while installing it fixes the issue, except in uswest it seems.

@RoyalOughtness
Copy link
Author

@RoyalOughtness
Copy link
Author

going to attempt a rebuild as a mitigation.

@praiskup praiskup reopened this Dec 6, 2024
@praiskup
Copy link
Member

praiskup commented Dec 6, 2024

Potentially one of the CDN nodes has a corrupt artifact?

That would explain it? Not sure. Reopening, please let us know how it goes - I don't seem to be able to reproduce this.

@RoyalOughtness
Copy link
Author

RoyalOughtness commented Dec 6, 2024

@praiskup the rebuild fixed it

¯\_(ツ)_/¯

@praiskup
Copy link
Member

praiskup commented Dec 6, 2024

Ok, thank you for the report @RoyalOughtness - if it appears again, please reopen, I would take a closer look. Sorry for the inconvenience.

@RoyalOughtness
Copy link
Author

No problem, will do

@nikromen nikromen moved this from Needs triage to Done in CPT Kanban Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants