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

Upgrading from 4.16 to 4.17 causes the Cluster Resource Override Operator to stop working

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 3
    • None
    • None
    • None
    • AUTOSCALE - Sprint 270
    • 1
    • Done
    • Bug Fix
    • Hide
      * Previously, the Cluster Resource Admission Override Operator failed to delete old secrets during upgrading from {product-title} 4.16 to {product-title} 4.17. This situation caused the Cluster Resource Override Admission Operator webhook to stop working and prevented pods from being created in namespaces that had the Cluster Resource Override Admission Operator enabled. With this release, old secrets are deleted, error handling by the Cluster Resource Override Admission Operator is improved, and the issue with creating pods in namespaces is resolved. (link:https://issues.redhat.com/browse/OCPBUGS-54886[OCPBUGS-54886])
      Show
      * Previously, the Cluster Resource Admission Override Operator failed to delete old secrets during upgrading from {product-title} 4.16 to {product-title} 4.17. This situation caused the Cluster Resource Override Admission Operator webhook to stop working and prevented pods from being created in namespaces that had the Cluster Resource Override Admission Operator enabled. With this release, old secrets are deleted, error handling by the Cluster Resource Override Admission Operator is improved, and the issue with creating pods in namespaces is resolved. (link: https://issues.redhat.com/browse/OCPBUGS-54886 [ OCPBUGS-54886 ])
    • None
    • None
    • None
    • None

      Description of problem:

      When the Cluster Resource Override Operator (CROO) is upgraded from v4.16 to v4.17 as a result of an OpenShift cluster upgrade, there are multiple errors:

When attempting to create a pod in a namespace with CROO enabled, the following error is seen:
~~~
Error from server (InternalError): error when creating "example.yaml": Internal error occurred: failed calling webhook 
"clusterresourceoverrides.admission.autoscaling.openshift.io": failed to call webhook: the server is currently unable to handle the request
~~~
Additionally, namespaces will fail to be deleted with the following error under status.conditions:
~~~
Discovery failed for some groups, 1 failing: unable to retrieve the complete list of server APIs: admission.autoscaling.openshift.io/v1: stale GroupVersion discovery: admission.autoscaling.openshift.io/v1
~~~

      Version-Release number of selected component (if applicable):

      clusterresourceoverride-operator.v4.17.0-202503210032
OpenShift 4.17 that was upgraded from 4.16

      How reproducible:

      I believe this should be reproducible every time, however I've only had time to test this once due to the upgrade involved.

      Steps to Reproduce:

      1. On a OpenShift 4.16 cluster, install the clusterresourceoverride operator from the stable channel.      
2. Create a clusterresourceoverride resource with default values. 
3. Upgrade the OpenShift cluster to 4.17. After the upgrade is complete, CROO will be automatically upgraded to v4.17 as well.     

      Actual results:

      There are errors and CROO doesn't work properly.     

      Expected results:

      There are no errors and CROO works properly.     

      Additional info:

              rh-ee-macao Max Cao
              rhn-support-cuthayak Clark Uthayakumar
              None
              None
              Paul Rozehnal Paul Rozehnal
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: