Hi Team, The Customer manually started the upgrade of the Red Hat Openshift Service Mesh operator, but it has been stuck in pending since the upgrade was started  (01/03)

Checking the events on the openshift-namespace operator, I noticed these warning messages: 

(⎈|rocpayh1.ejoj.p1:default)]$ oc get ev -n openshift-operators 
LAST SEEN   TYPE      REASON        OBJECT                                MESSAGE
15m         Warning   FailedMount   pod/istio-operator-6df7df9b4f-mzbct   MountVolume.SetUp failed for volume "webhook-cert" : secret "istio-operator-service-cert" not found
55s         Warning   FailedMount   pod/istio-operator-6df7df9b4f-mzbct   MountVolume.SetUp failed for volume "apiservice-cert" : secret "istio-operator-service-cert" not found

But since these are Warning-type messages, hence I am not sure if the missing secret is causing the upgrade to be stuck. Additionally, the Customer mentioned this: 

Yes, Red Hat Service Mesh Operator was working normally. The service mesh is still functioning as expected, only the operator is in a Pending state

Checking the olm-operator logs I found multiple `no owned roles found` errors, such as: 

$ oc logs olm-operator-79b4b5d959-29dvt -n openshift-operator-lifecycle-manager | tail -n 10
...
time="2025-01-07T15:14:17Z" level=info msg="couldn't ensure RBAC in target namespaces" csv=servicemeshoperator.v2.6.3 error="no owned roles found" id=Cs7fN namespace=openshift-operators phase=Pending
E0107 15:14:17.216453       1 queueinformer_operator.go:319] sync {"update" "openshift-operators/servicemeshoperator.v2.6.3"} failed: no owned roles found

I was wondering if uninstalling/reinstalling the operator could fix this issue, although the Customer mentioned this: Just to remind, we cannot stop the service mesh process during uninstalling/reinstalling the operator, especially the gateway that is responsible for the load balancer in AWS