• False
    • Hide

      None

      Show
      None
    • False

      Moved from Github issue

      When setting the flag `{}timeout 0` to `sonobuoy run [{-}-plugin manifest.yaml[ --plugin manifest.yaml]]` it's using 0 seconds as time out context, resulting in closing context with workers instead of `no timeout`.

      Sonobuoy server Logs:

      time="2022-03-29T16:59:48Z" level=info msg="Running plugin" plugin=openshift-provider-cert-level1
      time="2022-03-29T16:59:48Z" level=info msg="Running plugin" plugin=openshift-provider-cert-level2
      time="2022-03-29T16:59:48Z" level=info msg="Running plugin" plugin=openshift-provider-cert-level3
      time="2022-03-29T16:59:48Z" level=error msg="Timeout waiting for plugin openshift-provider-cert-level1. Try checking the pod logs and other data in the results tarball for more information."
      time="2022-03-29T16:59:48Z" level=info msg="received internal aggregator result" node=global plugin_name=openshift-provider-cert-level1
      time="2022-03-29T16:59:48Z" level=error msg="Timeout waiting for plugin openshift-provider-cert-level2. Try checking the pod logs and other data in the results tarball for more information."
      time="2022-03-29T16:59:48Z" level=info msg="received internal aggregator result" node=global plugin_name=openshift-provider-cert-level2
      time="2022-03-29T16:59:48Z" level=error msg="Timeout waiting for plugin openshift-provider-cert-level3. Try checking the pod logs and other data in the results tarball for more information."
      time="2022-03-29T16:59:48Z" level=info msg="received internal aggregator result" node=global plugin_name=openshift-provider-cert-level3
      time="2022-03-29T16:59:48Z" level=info msg="Last update to annotations on exit"
      time="2022-03-29T16:59:49Z" level=info msg="Shutting down aggregation server"
      time="2022-03-29T16:59:49Z" level=error msg="error running plugins: timeout occurred when waiting for plugin results"
      time="2022-03-29T16:59:49Z" level=error msg="Timeout occurred when running plugins. Inspect logs further for details." 

      The helper says:

      $ sonobuoy run -help
      --timeout int How long (in seconds) Sonobuoy aggregator will wait for plugins to complete before exiting. 0 indicates no timeout. (default 21600) 

      sonobuoy version:

      $ sonobuoy version
      Sonobuoy Version: v0.56.0
      MinimumKubeVersion: 1.17.0
      MaximumKubeVersion: 1.99.99
      GitSHA: 0665cd322b11bb40c2774776de765c38d8104bed 

      Steps to reproduce:
      1. run custom plugin:

      sonobuoy run \
      --dns-namespace openshift-dns \
      --dns-pod-labels=dns.operator.openshift.io/daemonset-dns=default \
      --timeout 0 \
      --plugin tools/plugins/openshift-provider-cert-level-1.yaml \
      --plugin tools/plugins/openshift-provider-cert-level-2.yaml \
      --plugin tools/plugins/openshift-provider-cert-level-3.yaml 

      2. Check the logs:

      oc logs sonobuoy -n sonobuoy
      

            rhn-support-rbost Robert Bost
            rhn-support-mrbraga Marco Braga
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 hour
                1h