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

[OLMv1] Fix for Boxcutter: Rollout restart of a deployment managed by OLM doesn't work as expected

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • 5
    • None
    • None
    • None
    • None
    • Rejected
    • Yanma Sprint 285
    • 1
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      A new RS is created but it gets immediately scaled down and the old RS takes over instead. For example:

      % oc rollout restart deployment openshift-pipelines-operator -n openshift-operators
      Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      True    MinimumReplicasAvailable
  Progressing    True    NewReplicaSetAvailable
OldReplicaSets:  openshift-pipelines-operator-6b84bd4dbd (0/0 replicas created)
NewReplicaSet:   openshift-pipelines-operator-75d5dddc64 (1/1 replicas created)
Events:
  Type    Reason             Age   From                   Message
  ----    ------             ----  ----                   -------
  Normal  ScalingReplicaSet  114s  deployment-controller  Scaled up replica set openshift-pipelines-operator-6b84bd4dbd from 0 to 1
  Normal  ScalingReplicaSet  113s  deployment-controller  Scaled down replica set openshift-pipelines-operator-6b84bd4dbd from 1 to 0

      What did you expect to see?
      A new Replica Set with a new set of pods comes up, replacing the existing RS.
      Upstream bug:
      https://github.com/operator-framework/operator-lifecycle-manager/issues/3392
       

              rh-ee-cmacedo Camila Macedo
              rhn-support-disharma Diksha Sharma
              Xia Zhao Xia Zhao
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: