Uploaded image for project: 'OpenShift Monitoring'
  1. OpenShift Monitoring
  2. MON-3093

End-to-end tests don’t run with HyperShift clusters because they are single node.

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • NEW
    • MON Sprint 240

      While running the e2e test locally with Hypershift cluster from cluster-bot I noticed that it fails on step waiting for 2 prometheus instances.

      “wait for prometheus-k8s: expected 2 Prometheus instances but got: 1: timed out waiting for the condition” 

      Since Hypershift clusters from cluster-bot are single worker node, it will always fail since we are checking it should be always 2 instances in main_test.go.

      Ideally we need to check the infrastructureTopology field and adjust the test if the infrastructure is “SingleReplica”

       

              mariofer@redhat.com Mario Fernandez Herrero
              janantha@redhat.com Jayapriya Pai
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: