Major As a follow up to ENTMQBR-2469 where an OperatorSource was created to allow the operator to be deployed on OCP 4, an update was made to better integrate the broker pods status with the OLM UI via PR#18 that was committed via 2783ed92d74949264727d2726354254ad7eae280
This resulted in logging messages like:
{"level":"info","ts":1568487367.47735,"logger":"olm","msg":"Found deployments with status ","stopped":[],"starting":["ex-aao-ss-4"],"ready":["ex-aao-ss-1","ex-aao-ss-2","ex-aao-ss-3"]}
{"level":"info","ts":1568487367.4773884,"logger":"package pods","msg":"PodStatus are to be updated.............................","ActiveMQArtemis Name":"ex-aao","info:":{"ready":["ex-aao-ss-1","ex-aao-ss-2","ex-aao-ss-3"],"starting":["ex-aao-ss-4"]}}
which have been absent in the logs since the v2alpha1 CRD work was completed via ENTMQBR-2687.
