Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-6336

Prometheus server port cannot be reused in the same CI job

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • openshift-4.21
    • openshift-4.19, openshift-4.20, openshift-4.21
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • 0
    • None
    • None
    • uShift Sprint 280
    • None
    • None
    • None

      Description of problem:

      Prometheus server port cannot be reused in the same CI job in multiple scenarios. Both optional and telemetry scenarios start a Prometheus server in the hypervisor. The Prometheus server starts in the hypervisor. When both scenarios are executed at the same time, this failure is reproducible,

      Version-Release number of selected component (if applicable):

      4.21, 4.20 and 4.19

      How reproducible:

      Sometimes, CI jobs fail unable to bind to ports

      Actual results:

      Observability (from Optional scenario) and Telemetry tests fail randomly

      Expected results:

      Observability (from Optional scenario) and Telemetry tests must pass

      Additional info:

      https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_microshift/5756/pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-release-arm/1991388130787201024 

              pmatusza@redhat.com Patryk Matuszak
              ggiguash@redhat.com Gregory Giguashvili
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: