sonobuoy status is still running when Remaining: 0

[nkuacac]

What steps did you take and what happened:
[A clear and concise description of what the bug is.]

sonobuoy status
PLUGIN STATUS RESULT COUNT PROGRESS
e2e complete 1 Passed:293, Failed: 63, Remaining: 0
systemd-logs complete 1
systemd-logs running 1

Sonobuoy is still running. Runs can take 60 minutes or more depending on cluster and plugin configuration.

sonobuoy retrieve
error retrieving results: no valid entries in result

│ e2e Ginkgo ran 1 suite in 6h18m16.705238664s
│ sonobuoy-worker time="2023-09-14T11:08:57Z" level=trace msg="Invoked command global with args [] and flags [level=trace logtostderr=true v=6]"
│ sonobuoy-worker time="2023-09-14T11:08:57Z" level=info msg="Waiting for waitfile" waitfile=/tmp/sonobuoy/results/done
│ sonobuoy-worker time="2023-09-14T11:08:57Z" level=info msg="Starting to listen on port 8099 for progress updates and will relay them to https://[192.168.32.80]:80
│ sonobuoy-worker time="2023-09-14T17:27:14Z" level=trace msg="Detected done file but sleeping for 5s then checking again for file. This allows other containers to
│ e2e Test Suite Failed
│ e2e 2023/09/14 17:27:13 Saving results at /tmp/sonobuoy/results
│ e2e 2023/09/14 17:27:13 running command: exit status 1
│ sonobuoy-worker time="2023-09-14T17:27:19Z" level=info msg="Detected done file, transmitting result file" resultFile=/tmp/sonobuoy/results/e2e.tar.gz

What did you expect to happen:
When running finish. we can get the result.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Sonobuoy version: Sonobuoy Version: v0.56.16
• Kubernetes version: (use kubectl version):v1.24.15
• Kubernetes installer & version:
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):
• Sonobuoy tarball (which contains * below)