Uploaded image for project: 'OpenShift SDN'
  1. OpenShift SDN
  2. SDN-3460

rename openshift org CI jobs to have proper CNI

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Normal
    • None
    • None
    • None
    • 3
    • False
    • None
    • False
    • ---
    • SDN Sprint 224, SDN Sprint 225, SDN Sprint 226, SDN Sprint 227, SDN Sprint 228, SDN Sprint 229, SDN Sprint 230, SDN Sprint 231, SDN Sprint 232, SDN Sprint 233, SDN Sprint 234, SDN Sprint 235, SDN Sprint 236, SDN Sprint 237, SDN Sprint 238, SDN Sprint 239, SDN Sprint 240, SDN Sprint 241, SDN Sprint 242, SDN Sprint 243, SDN Sprint 244, SDN Sprint 245
    • 0
    • 0.0

    Description

      by the end of 4.12, we no longer want to see any flakes in the test case
      "[sig-ci] [Early] prow job name should match network type [apigroup:config.openshift.io] [Suite:openshift/conformance/parallel]"

      this case will flake only if the job does not already have sdn or ovn in it's
      job name and will hard fail if the job name does have sdn or ovn and the
      actual CNI being used is not that.

      a quick one liner to get a list of jobs hitting this flake:
      (NETWORK needs to be set to ovn or sdn)

      w3m -dump -cols 200 "https://search.ci.openshift.org/?maxAge=336h&type=junit&search=job+name.*does+not+have+network+type+in+name.*expected.*${NETWORK}" | sed -n 's/^\([^ ]*\) .*failures match.*/\1/p' | grep -v rehearse | sort 

      This story is just to track ongoing work. assigning 3 points to it. will need to duplicate it every sprint to make this work visible to the team in jira.

      This work is also coming as a result of TRT-487 which will track the entire
      renaming effort.

      Attachments

        Activity

          People

            jluhrsen Jamo Luhrsen
            jluhrsen Jamo Luhrsen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: