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

error retrieving results: non-zero data ! (byte 33) read after tar EOF #1908

Open
katexochen opened this issue Apr 28, 2023 · 3 comments
Open
Labels

Comments

@katexochen
Copy link

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:

  • Sonobuoy version: v0.56.16
  • Kubernetes version: (use kubectl version): v1.27.0
  • Kubernetes installer & version: constellation (v2.8.0-pre, dev-build)
  • Cloud provider or hardware configuration: Azure
  • OS (e.g. from /etc/os-release): Fedora (custom)
  • Sonobuoy tarball (which contains * below)
@franknstyle
Copy link
Collaborator

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.

@katexochen
Copy link
Author

Are the log files/test outputs being retrieved from a large count of nodes

This was a cluster with 3 control planes and 2 worker nodes

or potentially large file sizes?

Our logs are usually ~3 MB.
We run the following plugins (in case that influences the file size):

--plugin e2e
--plugin-env e2e.E2E_FOCUS="\[Conformance\]" --plugin-env e2e.E2E_SKIP="for service with type clusterIP|HostPort validates that there is no conflict between pods with same hostPort but different hostIP and protocol"
--plugin https://raw.githubusercontent.com/vmware-tanzu/sonobuoy-plugins/master/cis-benchmarks/kube-bench-plugin.yaml
--plugin https://raw.githubusercontent.com/vmware-tanzu/sonobuoy-plugins/master/cis-benchmarks/kube-bench-master-plugin.yaml'

or is there increased latency in the network between sonobuoy CLI and the cluster the results bundle is being retrieved from

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.

Copy link

stale bot commented Dec 15, 2023

There has not been much activity here. We'll be closing this issue if there are no follow-ups within 15 days.

@stale stale bot added the stale label Dec 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants
@katexochen @franknstyle and others