Seen in the marketplace ClusterOperator early in a 4.3.18 -> 4.3.19 update:
version: operator 4.3.18
2020-05-05T23:31:20Z Progressing=False OperatorExited: The operator has exited
2020-05-19T06:39:39Z Available=False OperatorExited: The operator has exited
2020-05-05T23:31:00Z Upgradeable=True OperatorExited: Marketplace is upgradeable
2019-12-05T18:28:36Z Degraded=False OperatorExited: The operator has exited
Checking out the operator pod:
$ jq -r '.status | .startTime + " " + .phase + "\n" + ([.conditions | .lastTransitionTime + " " + (.lastProbeTime // "-") + " " + .type + "=" + .status + " " + (.reason // "-") + ": " + (.message // "-")] | join("\n"))' config/pod/openshift-marketplace/marketplace-operator-794975cff-h7m5f
2020-05-05T23:30:12Z - Initialized=True -: -
2020-05-19T06:39:42Z - Ready=False ContainersNotReady: containers with unready status: [marketplace-operator]
2020-05-19T06:39:42Z - ContainersReady=False ContainersNotReady: containers with unready status: [marketplace-operator]
2020-05-05T23:30:12Z - PodScheduled=True -: -
so it has been Pending with an unready container (and no restarts) for two weeks.
*** Bug 1888383 has been marked as a duplicate of this bug. ***
The PR closing this bug  just teaches the marketplace operator to not set OperatorExited on graceful shutdowns. That's good, it's the cluster-version operator's job to complain if the marketplace operator fails to come back up. But it does not address why the marketplace operator was unable to come back up (i.e. the "stuck" portion of this bug). If anyone has a cluster where the marketplace operator is not coming back up or sticking an update, regardless of OperatorExited conditions, please file a new bug and point us at a must-gather, and we'll dig in.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.