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

[release-4.14] When starting cluster update, nodes in paused MCPs begin updating

XMLWordPrintable

    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, Nodes of paused MachineConfigPools may be incorrectly unpaused when performing a cluster update. With this update, Nodes of paused MachineConfigPools correctly stay paused when performing a cluster update. (link: https://issues.redhat.com/browse/OCPBUGS-31839[*OCPBUGS-31839*]
      Show
      * Previously, Nodes of paused MachineConfigPools may be incorrectly unpaused when performing a cluster update. With this update, Nodes of paused MachineConfigPools correctly stay paused when performing a cluster update. (link: https://issues.redhat.com/browse/OCPBUGS-31839 [* OCPBUGS-31839 *]
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-23319. The following is the description of the original issue:
      —
      Description of problem:

      When using canary rollout, paused MCPs begin updating when the user triggers the cluster update.

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

       

      How reproducible:

      Approximately 3/10 times that I have witnessed.

      Steps to Reproduce:

      1. Install cluster
2. Follow canary rollout strategy: https://docs.openshift.com/container-platform/4.11/updating/update-using-custom-machine-config-pools.html 
3. Start cluster update

      Actual results:

      Worker nodes in paused MCPs begin update

      Expected results:

      Worker nodes in paused MCPs will not begin update until cluster admin unpauses the MCPs

      Additional info:

      This has occurred with my customer in their Azure self-managed cluster and their on-prem cluster in vSphere, as well as my lab cluster in vSphere.

              rhn-engineering-rhamilto Robb Hamilton
              openshift-crt-jira-prow OpenShift Prow Bot
              YaDan Pei YaDan Pei
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: