sonobuoy: sonobuoy retrieve cmd returns error: "error retrieving results: unexpected EOF"
What steps did you take and what happened: Step 1: ran the pre-packaged systemd-logs plugin: sonobuoy run --plugin systemd-logs --dns-pod-labels dns.operator.openshift.io/daemonset-dns=default --dns-namespace openshift-dns
Step 2: Checked the status of the plugin after a while:
sonobuoy status
Output:
Step 3: Tried to download the results tar file
sonobuoy retrieve
Output:
What did you expect to happen: I expected Step 3 above to run successfully without any error messages. Note: After Step 3 throws error, I still see a result tar file but it is corrupt and throws error during extraction.
Anything else you would like to add: Steps to provision the cluster https://docs.openshift.com/container-platform/4.9/installing/installing_azure/installing-azure-account.html
Environment:
- Sonobuoy version: v0.56.2
- Kubernetes version: (use
kubectl version): v1.22.0-rc.0+a44d0f0 - Kubernetes installer & version: Openshift Container Platform , version: 4.9.5
- Cloud provider or hardware configuration: Azure cloud
- OS (e.g. from
/etc/os-release):
- Sonobuoy tarball (which contains * below)
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 28 (11 by maintainers)
o/ For sure! I will sync with the team and submit it soon.
For us, max 10 retries with two seconds of interval is working well. I had only one exception in my labs when I was using an very slow internet connection and tried to retrieve results. I believe it’s a combination of the size and the connection between the cli and API when streaming the tarball.
@mdrakiburrahman we implemented it on the backend in Golang, if you are not working on open the PR, I can port it to the sonobuoy’s retrieve client. Let me know.
Hi @mdrakiburrahman, thanks for the input and apologies in slow responses as we are going through changes in maintainers.
To answer your question, yes, we will be happy to accept a PR. cc @franknstyle