Uploaded image for project: 'OCP Technical Release Team'
  1. OCP Technical Release Team
  2. TRT-2554

aggregated-hypershift-ovn-conformance kas-connection-checker failures

XMLWordPrintable

    • Icon: Ticket Ticket
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None

      Starting with 4.22.0-0.nightly-2026-02-16-211851, the aggregated-hypershift-ovn-conformance-4.22 jobs started failing these three tests related to kas-connection-checker:

      : [sig-arch] Managed cluster should ensure platform components have system-* priority class associated [Suite:openshift/conformance/parallel] expand_less 	0s
      {  fail [github.com/openshift/origin/test/extended/pods/priorityclasses.go:93]: 
      3 pods found with invalid priority class (should be openshift-user-critical or begin with system-):
      kube-system/kas-connection-checker-4fbbt (currently "")
      kube-system/kas-connection-checker-594hk (currently "")
      kube-system/kas-connection-checker-5g42g (currently "")}
      
      : [sig-arch] Managed cluster should ensure control plane pods do not run in best-effort QoS [Suite:openshift/conformance/parallel] expand_less 	0s
      {  fail [github.com/openshift/origin/test/extended/operators/qos.go:78]: 
      3 pods found in best-effort QoS:
      kube-system/kas-connection-checker-4fbbt is running in best-effort QoS
      kube-system/kas-connection-checker-594hk is running in best-effort QoS
      kube-system/kas-connection-checker-5g42g is running in best-effort QoS}
      
      : [sig-arch] Managed cluster should set requests but not limits [Suite:openshift/conformance/parallel] expand_less 	0s
      {  fail [github.com/openshift/origin/test/extended/operators/resources.go:244]: Pods in platform namespaces are not following resource request/limit rules or do not have an exception granted:
        apps/v1/DaemonSet/kube-system/kas-connection-checker/container/connection-checker does not have a cpu request (rule: "apps/v1/DaemonSet/kube-system/kas-connection-checker/container/connection-checker/request[cpu]")
        apps/v1/DaemonSet/kube-system/kas-connection-checker/container/connection-checker does not have a memory request (rule: "apps/v1/DaemonSet/kube-system/kas-connection-checker/container/connection-checker/request[memory]")}
      

      Example failing job: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-ovn-conformance/2023508394500952064

      Looking at https://amd64.ocp.releases.ci.openshift.org/releasestream/4.22.0-0.nightly/release/4.22.0-0.nightly-2026-02-16-211851?from=4.22.0-0.nightly-2026-02-16-121727 the following PR seems to bring related functionality (but it is suspicous for a o/hypershift PR to not test this? all presubmits passed there).

      https://github.com/openshift/hypershift/pull/7489

              Unassigned Unassigned
              afri@afri.cz Petr Muller
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: