AMQ Broker Operator installation becomes unusable after supplying improper CR

1) Create an operator deployment 2) Create a CR which would list storage limitation as follows: storage: size: 1 (integer without units) (operator fails to create stateful set here due to underlying kube errors, this is expected and proper)     3) Delete CR   4) Create a new CR which would list proper storage limitations   5) See log for consequences (operator claims that "stateful set ex-aao-ss is not found" before even trying to create it)

If you configure the `storage.size` property of a Custom Resource (CR) instance to specify the size of the Persistent Volume Claim (PVC) required by brokers in a deployment for persistent storage, the Operator installation becomes unusable if you do not specify this value properly. For example, suppose that you set the value of `storage.size` to `1` (that is, without specifying a unit). In this case, the Operator cannot use the CR to create a broker deployment. In addition, even if you remove the CR and deploy a new version with `storage.size` specified correctly, the Operator still cannot use this CR to create a deployment as expected. To work around this issue, first stop the Operator. In the OpenShift Container Platform web console, click *Deployments*. For the Pod that corresponds to the AMQ Broker Operator, click the *More options* menu (three vertical dots). Click *Edit Pod Count* and set the value to `0`. When the Operator Pod has stopped, create a new version of the CR with `storage.size` correctly specified. Then, to restart the Operator, click *Edit Pod Count* again and set the value back to `1`.