Uploaded image for project: 'Multiple Architecture Enablement'
  1. Multiple Architecture Enablement
  2. MULTIARCH-4548

Repeated testcase failure in 4.16 libvirt runs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 4.16.0
    • IBM P CI
    • None
    • False
    • None
    • False
    • NEW
    • NEW

      14 testcases failed in 4.16 libvirt runs, with a common error
      Error: 

      { backend-disruption-name/cache-oauth-api-reused-connections connection/reused disruption/openshift-tests was unreachable during disruption: for at least 39s (maxAllowed=6s): P99 from historical data for similar jobs over past 3 weeks: 0s rounded P99 up to always allow one second added an additional 5s of grace Mar 22 06:13:41.336 - 1s E backend-disruption-name/cache-oauth-api-reused-connections connection/reused disruption/openshift-tests reason/DisruptionBegan request-audit-id/eedd1878-5762-49d5-9f87-d5735ef6dc0a backend-disruption-name/cache-oauth-api-reused-connections connection/reused disruption/openshift-tests stopped responding to GET requests over reused connections: Get "https://api.libvirt-ppc64le-0-2-4da8e.libvirt-ppc64le-0-2.ci:6443/apis/oauth.openshift.io/v1/oauthclients?resourceVersion=0": net/http: timeout awaiting response headers Mar 22 06:13:42.336 - 37s E backend-disruption-name/cache-oauth-api-reused-connections connection/reused disruption/openshift-tests reason/DisruptionBegan request-audit-id/dcf9a5e3-856f-4f33-9117-eee843ce12b0 backend-disruption-name/cache-oauth-api-reused-connections connection/reused disruption/openshift-tests stopped responding to GET requests over reused connections: Get "https://api.libvirt-ppc64le-0-2-4da8e.libvirt-ppc64le-0-2.ci:6443/apis/oauth.openshift.io/v1/oauthclients?resourceVersion=0": net/http: TLS handshake timeout}

      Joblink

              shgokul Shilpa Gokul
              sgudaji1 Suraj Gudaji
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: