-
Notifications
You must be signed in to change notification settings - Fork 6
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
Potentially corrupt blob #19
Comments
This is, hopefully, fixed by the digest checking added in v0.4.4 |
We'd be happy to test this out! We see this issue fairly frequently across our systems, so we should be able to validate if it's gone. We're upgrading from 0.3.8, is there anything we should be aware of while upgrading? I don't see upgrade notes anywhere, not sure if I'm looking in the right place |
@thejosephstevens you shouldn't need to do anything special, the only reason I bumped from v0.3 to v0.4 is because of an additional feature added to URL parsing to support CRI-O. I'm uploading v0.4.5 now to fix an issue with enabling this digest checking feature in the helm chart. |
Haven't narrowed it down yet, but ran into this pull error which went away when I cleared our the S3 bucket:
Same deal when trying to pull directly from the node too:
I'm guessing the blob being pulled somehow got into a funky state in the bucket since the issue went away after I cleared out the S3 bucket, need to dig in more but wanted to put this into an issue in case anyone knew what might have happened. Thanks!
The text was updated successfully, but these errors were encountered: