im re-opening this BZ as cu is still having issues, this time it seems w the messageSize for the installPlan to update its status. can i get some guidance as to where that configuration may be, please?
kevin, thank-you for picking this up. ive passed on the request to the cu but have yet to hear a response. previously he had included an inspection on the namespace (oc adm inspect ns/cp4i) as well as one for the OLM operator: would those suffice in the meantime? milti
We specifically need the yaml representation of all the Subscription objects in the namespace (so that we can recreate them on a test cluster). The full catalog-operator log in the openshift-operator-lifecycle-manager would also be helpful.
subscription requested has been attached: is there any further request before you can proceed to work on this ticket?
Discussed this issue with Kevin and Daniel. They suggested us to try the same procedure using the same OLM commit locally (https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/install/install.md#run-locally-with-minikube). With that procedure, InstallPlan was created successfully and all dependency resolution worked. I'm attaching the yaml output as evidence. There's some issues that avoided QE to test the same issue on 4.7 that is not related with this one, therefore since the objective of this issue is to backport to 4.6, I'll mark it as VERIFIED and other issues should be tracked with a separated bzs.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633