S3 upload Failed (maybe due to big file)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- kubernetes, rust
- Domain
- cloud, infrastructure
Research direction
No source files or tests are named. Start by reproducing the upload with the kubectl run segfaulter command and compare it with the larger core dump reported for versions 8.10.0 and 9.0.0. Determine why the S3-compatible upload returns 200 with no object or 404 NoSuchUpload, then verify that larger dumps are stored successfully.
Written by the indexing model from the issue text.
Description
We faced an issue on both versions 8.10.0 and 9.0.0
The core dump handler is able to see a crash,
on 8.10.0
Uploading: var/mnt/core-dump-handler/cores/<>.zip
zip size is 10115781
S3 Returned: 200
But there is no file in S3 bucket
in 9.0.0 the situation is different
Uploading: var/mnt/core-dump-handler/cores/<>.zip
zip size is 10864637
Upload Failed Got HTTP 404 with content '
core-dump-handler-mk4xh coredump-containerNoSuchUploadThe specified upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed. <.......> '
But there is no file in S3 bucket
while testing via
kubectl run -i -t segfaulter --image=quay.io/icdh/segfaulter --restart=Never`
All works as expected.
I
see that the dump failed is much bigger than one created while segfaulter crashed.
Does Core-Dump-Handler have limitations?
Any suggestions on how to solve it?
- Dominant language
- Rust
- Stars
- 160
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from IBM/core-dump-handler
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
IBM/core-dump-handler#187 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
IBM/core-dump-handler#188 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
IBM/core-dump-handler#185 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
IBM/core-dump-handler#179 · 4 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
IBM/core-dump-handler#178 · 1 comment ·
All issues in IBM/core-dump-handler
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug team:backend track:services-maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cowprotocol/services#4950 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·