If the AMQ Broker Operator encounters an error when applying a Custom Resource (CR) update, the Operator does not recover. Specifically, the Operator stops responding as expected to further updates to your CRs. For example, say that a misspelling in the value of the image attribute in your main broker CR causes broker Pods to fail to deploy, with an associated error message of `ImagePullBackOff`. If you then fix the misspelling and apply the CR changes, the Operator does not deploy the specified number of broker Pods. The Operator does not respond to any further CR changes. To work around this issue, you must delete any pods with the status `Pending` and let the Operator recreate them. To check which pods have the status `Pending`, use a command such as `kubectl get pods --field-selector=status.phase=Pending`.

Deploy the operator and CRDs as per documentation. Create valid broker deployment with correctly filled values in custom resource. Make sure the pod(s) is (are) running. Change the image in custom resource to different valid version and update CR instance. Make sure the pod(s) is (are) running. Modify CR to cause erroneous state - make typo in image path or other - and apply changes. Check that pod(s) couldn't be deployed. Fix the CR and apply changes. Check operator logs (operator sholud be avere of changes in CR). Check the stateful set - Nothing has happen and it's hanging in the erroneous state.