Update from OpenShift Container Platform 4.10 to 4.11 stuck because kubelet on Node won't start because of feature gate CSIMigrationOpenStack is set to false

Solution Verified - Updated -

Issue

  • Node stuck in NotReady, SchedulingDisabled due to the below log:

    Nov 09 12:22:15 node.example.com hyperkube[1168976]: Error: failed to set feature gates from initial flags-based config: cannot set feature gate CSIMigrationOpenStack to false, feature is locked to true
    
  • Updating one cluster from 4.10.39 to 4.11.13 failed. While updating the first master node, something seemingly went wrong as the master node never reconnected to the cluster. When checking we found the below messages for kubelet.service

    Nov 22 07:36:22 master-01 hyperkube[15639]: Error: failed to set feature gates from initial flags-based config: cannot set feature gate CSIMigrationOpenStack to false, feature is locked to true
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4.11

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content