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

The kube-scheduler-RevisionController write and try to decrease latest revision.

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • Customer Escalated, Customer Reported
    • In Progress
    • Bug Fix
    • Hide
      Before this update, the `RevisionController` in core operators prevented upgrades to new revisions during a cluster upgrade if the `operator.openshift.io/revision-ready` annotation was missing on the latest available revision ConfigMap. With this release, the `RevisionController` logic was updated to upgrade to a new revision even if the `operator.openshift.io/revision-ready` annotation is missing. As a result, core operators can successfully transition to new revisions regardless of the annotation's presence. (link:https://issues.redhat.com/browse/OCPBUGS-58412[OCPBUGS-58412])
      Show
      Before this update, the `RevisionController` in core operators prevented upgrades to new revisions during a cluster upgrade if the `operator.openshift.io/revision-ready` annotation was missing on the latest available revision ConfigMap. With this release, the `RevisionController` logic was updated to upgrade to a new revision even if the `operator.openshift.io/revision-ready` annotation is missing. As a result, core operators can successfully transition to new revisions regardless of the annotation's presence. (link: https://issues.redhat.com/browse/OCPBUGS-58412 [ OCPBUGS-58412 ])
    • None
    • None
    • None
    • None

      Description of problem:

      Issue: 
      
      The kube-scheduler-RevisionController write and try to decrease latest revision.
      ~~~
      'RevisionControllerDegraded: unable to ApplyStatus for operator using fieldManager "kube-scheduler-RevisionController": KubeScheduler.operator.openshift.io "cluster" is invalid status.latestAvailableRevision: Invalid value: "integer":must only increase'
      ~~~
      ==========================================================================
      Environment: 
      
      Customer is facing this issue while upgrading from 4.17.15 to 4.18.17
      ==========================================================================
      The following Jira describes the similar issue with `kube-apiserver` component which has been fixed in 4.19 and backported to 4.18.
      - https://issues.redhat.com/browse/OCPBUGS-48276

       

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

          4.17

              fkrepins@redhat.com Filip Krepinsky
              rhn-support-harspati Harshada Patil
              Rama Kasturi Narra, Ying Zhou
              None
              Ying Zhou Ying Zhou
              None
              Votes:
              0 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: