Follow up to https://issues.redhat.com/browse/OCPBUGS-54568.  The missing priority class issue was fixable for istiod but needed to be overridden for servicemesh-operator3.  This task tracks the revert of the override.


In the e2e test logs we found below error message

    2 pods found with invalid priority class (should be openshift-user-critical or begin with system-):

openshift-ingress/istiod-openshift-gateway-57c5c5ccb9-pnpx7 (currently "")
openshift-operators/servicemesh-operator3-6b4fb78799-9qpzv (currently "")

    4.19.0-0.nightly-2025-04-02-170034

    100%

    1. trigger e2e extended test with gatewayapi tests
    2.
    3.
    

servicemesh-operator3 requirement for priorityclass was overridden

servicemesh-operator3 requirement for priorityclass should be restored and tests working once a solution is found

    longer message:

[sig-arch] Managed cluster should ensure platform components have system-* priority class associated [Suite:openshift/conformance/parallel]
  github.com/openshift/origin/test/extended/pods/priorityclasses.go:38
    STEP: Creating a kubernetes client @ 04/02/25 22:37:14.882
  I0402 22:37:14.883884  132172 discovery.go:214] Invalidating discovery information
    [FAILED] in [It] - github.com/openshift/origin/test/extended/pods/priorityclasses.go:79 @ 04/02/25 22:37:15.092
  • [FAILED] [0.219 seconds]
  [sig-arch] Managed cluster should [It] ensure platform components have system-* priority class associated [Suite:openshift/conformance/parallel]
  github.com/openshift/origin/test/extended/pods/priorityclasses.go:38

    [FAILED] 
    2 pods found with invalid priority class (should be openshift-user-critical or begin with system-):
    openshift-ingress/istiod-openshift-gateway-57c5c5ccb9-pnpx7 (currently "")
    openshift-operators/servicemesh-operator3-6b4fb78799-9qpzv (currently "")