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

When starting cluster update, nodes in paused MCPs begin updating

    XMLWordPrintable

Details

    • 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-23319[*OCPBUGS-23319*]
      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-23319 [* OCPBUGS-23319 *]
    • Bug Fix
    • In Progress

    Description

      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.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-31839 [release-4.15] When starting cluster update, nodes in paused MCPs begin updating

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-31839 [release-4.15] When starting cluster update, nodes in paused MCPs begin updating

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified
          links to

          GitHub openshift/console#13717: OCPBUGS-23319: fix bug where paused MCPs were incorrectly unpausing w…

          Activity

            People

              rhn-engineering-rhamilto Robb Hamilton
              rhn-support-adolling Adam Dollinger
              Yanping Zhang Yanping Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated: