= {prod2} Operator installing an additional {devworkspace} Operator Currently, under certain conditions, such as link: https://docs.openshift.com/container-platform/4.10/operators/understanding/olm/olm-understanding-olm.html [OLM] restart or cluster upgrade, the {prod2} Operator for {prod-short} 3.0.0 might automatically install the {devworkspace} Operator even if it is already present on the cluster. This might cause severe consequences: the {platforms-name} web terminal might stop working, or the {devworkspace} Operator admission webhooks might not work properly, which might affect the behavior of the cluster. You can detect this issue on your cluster by checking *Installed Operators* in the {platforms-name} web console: if this problem is occurring, you see multiple entries for the {devworkspace} Operator or one entry that is stuck in a loop of *Replacing* and *Pending*. .Workaround * On {platforms-name} 4.10.23 or earlier, enable the subscription for automated updates and get {prod-short} 3.0.1 through the link: https://docs.openshift.com/container-platform/4.10/operators/understanding/olm/olm-understanding-olm.html [OLM]. * On {platforms-name} 4.10.24 or later, follow the linked link: https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.0/html-single/administration_guide/index#repairing-the-devworkspace-operator-on-openshift [instructions] for fixing the cluster.