Bug 1880473

Summary: IBM Cloudpak operators installation stuck "UpgradePending" with InstallPlan status updates failing due to size limitation
Product: OpenShift Container Platform Reporter: Rob Gregory <rgregory>
Component: OLMAssignee: Haseeb Tariq <htariq>
OLM sub component: OLM QA Contact: Bruno Andrade <bandrade>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: urgent CC: bandrade, bluddy, dsover, htariq, jiazha, krizza, marobrie, mleonard, sgarciam, vlaad
Version: 4.5Keywords: Reopened
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:18:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1886223    

Comment 8 milti leonard 2020-09-28 16:28:06 UTC
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?

Comment 10 milti leonard 2020-09-29 16:26:20 UTC
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

Comment 11 Kevin Rizza 2020-09-29 16:38:41 UTC
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.

Comment 14 milti leonard 2020-10-05 15:44:30 UTC
subscription requested has been attached: is there any further request before you can proceed to work on this ticket?

Comment 27 Bruno Andrade 2020-10-09 16:52:28 UTC
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.

Comment 34 errata-xmlrpc 2021-02-24 15:18:37 UTC
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