Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-36858

CI failure: dualstack-upi

XMLWordPrintable

    • +
    • None
    • 3
    • ShiftStack Sprint 258, ShiftStack Sprint 259
    • 2
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      dualstack-upi jos are failing, and results may suggest the inability of the cloud to handle the workload. Is there a capacity issue?

       

      examples:

      4.16: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-shiftstack-ci-release-4.16-e2e-openstack-dualstack-upi/1810325585575022592

      4.17: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-shiftstack-ci-release-4.17-e2e-openstack-dualstack-upi/1810325860511649792 ("Etcd logged 10019 'took too long' messages, this test fails on any value over 10000 as this is a strong indicator that etcd was very unhealthy throughout the run. This can cause sparodic e2e failures and disruption and typically indicates faster disks are needed. These log message intervals are included in spyglass chart artifacts and can be used to correlate with disruption and failed tests")

              rh-ee-mcarpio Miguel Carpio
              pprinett@redhat.com Pierre Prinetti
              Itshak Brown Itshak Brown
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: