Details
-
Bug
-
Resolution: Done
-
Medium
-
None
Description
When Sonobuoy has completed the execution of conformance test and is reporting a failure as a result, the Robot testcase running Sonobuoy never completes.
# kubectl get po -n heptio-sonobuoy NAME READY STATUS RESTARTS AGE sonobuoy 1/1 Running 0 4h53m # # sonobuoy status PLUGIN STATUS COUNT e2e complete 1 systemd_logs failed 5 Sonobuoy has failed. You can see what happened with `sonobuoy logs`. # # sonobuoy logs namespace="heptio-sonobuoy" pod="sonobuoy" container="kube-sonobuoy" time="2019-06-24T07:37:37Z" level=info msg="Scanning plugins in ./plugins.d (pwd: /)" <...snip...> time="2019-06-24T10:36:37Z" level=info msg="Gracefully shutting down plugins due to timeout." time="2019-06-24T10:37:01Z" level=info msg="received aggregator request" client_cert=e2e plugin_name=e2e time="2019-06-24T10:37:01Z" level=info msg="Last update to annotations on exit" time="2019-06-24T10:37:01Z" level=info msg="Running non-ns query" time="2019-06-24T10:37:01Z" level=error msg="error querying CustomResourceDefinitions: the server could not find the requested resource" <...snip...> time="2019-06-24T10:37:19Z" level=info msg="Results available at /tmp/sonobuoy/201906240737_sonobuoy_376a4ddc-4498-49fc-af2e-999242c4c245.tar.gz" time="2019-06-24T10:37:19Z" level=info msg="no-exit was specified, sonobuoy is now blocking" #
