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
error retrieving results: non-zero data ! (byte 33) read after tar EOF #1908
Comments
Hi @katexochen I believe this may be related to #1633. There is a WIP pull request to add retries though I believe this to be a race condition between the initial calling function spawning a go routine to fetch the asset and returning pre-emptively a reader that may or may not be populated. To help in attempting reproduction. I have a few more questions. Are the log files/test outputs being retrieved from a large count of nodes, or potentially large file sizes? or is there increased latency in the network between sonobuoy CLI and the cluster the results bundle is being retrieved from. |
This was a cluster with 3 control planes and 2 worker nodes
Our logs are usually ~3 MB.
Might be the case. The network between GitHub runner and major cloud providers is quite slow from time to time. But no other indication for slow network in this specific run. |
There has not been much activity here. We'll be closing this issue if there are no follow-ups within 15 days. |
What steps did you take and what happened:
Running
sonobuoy retrieve --kubeconfig constellation-admin.conf
in a CI run.What did you expect to happen:
Getting the results. What causes this type of error?
Environment:
kubectl version
): v1.27.0/etc/os-release
): Fedora (custom)The text was updated successfully, but these errors were encountered: