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

[4.15] 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: Done-Errata
    • Icon: Major Major
    • None
    • 4.13, 4.12, 4.14, 4.15, 4.16, 4.17
    • OLM
    • Important
    • No
    • YellowJacket OLM Sprint 259
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, When the Operator Lifecycle Manager (OLM) evaluated a potential upgrade, it used the dynamic client list for all custom resource (CR) instances in the cluster. For clusters with a large number of CRs, that could result in timeouts from the apiserver and stranded upgrades. With this release, the issue is resolved. (link:https://issues.redhat.com/browse/OCPBUGS-41819[*OCPBUGS-41819*])
      __________
      When OLM evaluates a potential upgrade, it used the dynamic client lister for all CR instances in the cluster. For clusters with a large number of CRs that could result in timeouts from the apiserver and stranded upgrades where the only workaround was to uninstall/reinstall impacted operators.
      Show
      * Previously, When the Operator Lifecycle Manager (OLM) evaluated a potential upgrade, it used the dynamic client list for all custom resource (CR) instances in the cluster. For clusters with a large number of CRs, that could result in timeouts from the apiserver and stranded upgrades. With this release, the issue is resolved. (link: https://issues.redhat.com/browse/OCPBUGS-41819 [* OCPBUGS-41819 *]) __________ When OLM evaluates a potential upgrade, it used the dynamic client lister for all CR instances in the cluster. For clusters with a large number of CRs that could result in timeouts from the apiserver and stranded upgrades where the only workaround was to uninstall/reinstall impacted operators.
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-41677. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-41549. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-35358. The following is the description of the original issue:
      —
      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
              openshift-crt-jira-prow OpenShift Prow Bot
              Jian Zhang Jian Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: