Description of problem

Conformance tests are failing because global-pull-secret-syncer pods in the kube-system namespace do not have the required priority class set. The conformance test expects all pods to have either
"openshift-user-critical" priority class or a priority class that begins with "system-", but these pods have an empty priority class.

Version-Release number

4.21

How reproducible

Always

Steps to Reproduce

1. Run the conformance test suite on a HyperShift ROSA cluster
2. Execute the priority class validation test at github.com/openshift/origin/test/extended/pods/priorityclasses.go:93
3. Observe the test failure

Actual results

The conformance test fails with:

  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/global-pull-secret-syncer-g4cq7 (currently "")
  kube-system/global-pull-secret-syncer-lsf25 (currently "")
  kube-system/global-pull-secret-syncer-s7wdq (currently "")
  

Expected results

All pods should have valid priority classes set. The global-pull-secret-syncer pods should have either "openshift-user-critical" or a priority class beginning with "system-".

Additional info

• PROW job: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-aws-ovn-conformance/1989199961836752896
• Slack discussion: https://redhat-internal.slack.com/archives/C01CQA76KMX/p1763111618828019
• Root cause PR: https://github.com/openshift/hypershift/pull/6745
• Test failure location: github.com/openshift/origin/test/extended/pods/priorityclasses.go:93
• Affected pods: global-pull-secret-syncer pods in kube-system namespace
• Platform: ROSA HCP (AWS)
• Test suite: periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-aws-ovn-conformance