Uploaded image for project: 'Distributed Tracing'
  1. Distributed Tracing
  2. TRACING-1439

DaemonsetTest is failing intermittently

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • jaeger-1.20.0
    • None
    • None
    • None
    • Tracing Sprint #45

      TestDaemonSetSuite/TestDaemonSet is currently failing intermittently.  I did 2 sets of 10 runs on minikube and each time it failed on odd numbered runs but passed on the even numbered runs.  I set SAVE_LOGS but don't see anything of note in any of the logs for any run.

      partenon Can  you confirm that this began with Jaeger Operator PR 1170 or had you seen it earlier?

      Some, but not all, of the tests that fail display warning events of two different types.

      First:

      level=warning msg="Event Warning: Reason: FailedToUpdateEndpoint Message: Failed to update endpoint osdk-e2e-2aba4a4f-a0b2-4759-92a4-ef3e94ed2b27/agent-as-daemonset-agent: Operation cannot be fulfilled on endpoints \"agent-as-daemonset-agent\": the object has been modified; please apply your changes to the latest version and try again

      OR

      time="2020-08-27T17:42:37+02:00" level=info msg="Warning events for test TestDaemonSetSuite/TestDaemonSet"
      time="2020-08-27T17:42:37+02:00" level=warning msg="Event Warning: Reason: FailedMount Message: MountVolume.SetUp failed for volume \"agent-as-daemonset-ui-configuration-volume\" : failed to sync configmap cache: timed out waiting for the condition"
      time="2020-08-27T17:42:37+02:00" level=warning msg="Event Warning: Reason: FailedMount Message: MountVolume.SetUp failed for volume \"agent-as-daemonset-token-q2wtt\" : failed to sync secret cache: timed out waiting for the condition"

       

       

       

              jpkroehling@redhat.com Juraci Paixão Kröhling (Inactive)
              kearls@redhat.com Kevin Earls (Inactive)
              Distributed Tracing
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: