Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-35358

Install plan is unable to move forward and is stuck in Pending state when the amount of CRs is too high.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 4.13, 4.12, 4.14, 4.15, 4.16, 4.17
    • OLM
    • Important
    • No
    • Veritas OLM Sprint 256, YellowJacket OLM Sprint 259
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, Operators with many custom resources (CRs) exceeded API server timeouts. As a result, the install plan for the Operator got stuck in a pending state. This update fixes the issue by adding a page view for list CRs deployed on the cluster. (link:https://issues.redhat.com/browse/OCPBUGS-35358[*OCPBUGS-35358*])
      Show
      * Previously, Operators with many custom resources (CRs) exceeded API server timeouts. As a result, the install plan for the Operator got stuck in a pending state. This update fixes the issue by adding a page view for list CRs deployed on the cluster. (link: https://issues.redhat.com/browse/OCPBUGS-35358 [* OCPBUGS-35358 *])
    • Bug Fix
    • Done
    • Customer Escalated

      I'm working with the Gitops operator (1.7)  and when there is a high amount of CR (38.000 applications objects in this case) the related install plan get stuck with the following error:

       

      - lastTransitionTime: "2024-06-11T14:28:40Z"
          lastUpdateTime: "2024-06-11T14:29:42Z"
          message: 'error validating existing CRs against new CRD''s schema for "applications.argoproj.io":
            error listing resources in GroupVersionResource schema.GroupVersionResource{Group:"argoproj.io",
            Version:"v1alpha1", Resource:"applications"}: the server was unable to return
            a response in the time allotted, but may still be processing the request' 

      Even waiting for a long time the operator is unable to move forward not removing or reinstalling its components.

       

      Over a lab, the issue was not present until we started to add load to the cluster (applications.argoproj.io) and when we hit 26.000 applications we were not able to upgrade or reinstall the operator anymore.

       

              rh-ee-jkeister Jordan Keister
              rhn-gps-alfredo Alfredo Pizarro
              Jian Zhang Jian Zhang
              Michael Peter Michael Peter
              Votes:
              4 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated: