Description of problem: new operator called address-space-controller is installed during a 4.5.13 upgrade (from 4.5.11) Version-Release number of selected component (if applicable): 4.5.13 How reproducible: untested Steps to Reproduce: 1. install 4.5.11 cluster 2. upgrade to 4.5.13 3. Actual results: notice alerting on controller not starting Expected results: pod starts and runs without issues Additional info:
Did up do something with AMQ around the same time? I don't recognize "address-space-controller" as part of the core platform. But I did find reference in AMQ docs. Here they describe the permissions needed. https://access.redhat.com/documentation/en-us/red_hat_amq/7.2/html-single/using_amq_online_on_openshift_container_platform/index#ref-address-space-example-exporting-endpoints-messaging
(In reply to Eric Paris from comment #3) > Did up do something with AMQ around the same time? I don't recognize > "address-space-controller" as part of the core platform. But I did find > reference in AMQ docs. Here they describe the permissions needed. > > https://access.redhat.com/documentation/en-us/red_hat_amq/7.2/html-single/ > using_amq_online_on_openshift_container_platform/index#ref-address-space- > example-exporting-endpoints-messaging Yeah, that's my suspicion. Apparently, "console" and "address-space-controller" is running fine in the AMQ namespace $ oc get deployments -n amq-online NAME READY UP-TO-DATE AVAILABLE AGE address-space-controller 1/1 1 1 6d12h console 1/1 1 1 6d12h enmasse-operator 1/1 1 1 6d12h So why is it (trying) to run it in openshift-operators too? $ oc get deployments -n openshift-operators NAME READY UP-TO-DATE AVAILABLE AGE address-space-controller 0/1 0 0 6d12h console 1/1 1 1 6d12h container-security-operator 1/1 1 1 60d openshift-pipelines-operator 1/1 1 1 88d
So it is not an issue of Openshift or AMQ Online, seems someone during testing installed AMQ Online 1.5.x as cluster wide operator into openshift-operators, then uninstall and install again into specific namespace. But for AMQ Online operator uninstall using catalog is not enough. So this situation caused not ready pods. I can confirm that AMQ Online operator works fine after upgrade ocp 4.5.11 to 4.5.13. There is doc about uninstall amq online https://access.redhat.com/documentation/en-us/red_hat_amq/7.7/html/installing_and_managing_amq_online_on_openshift/assembly-uninstalling-messaging#uninstalling-olm-messaging