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

Azure CSI Driver operator has incorrect node selector for HyperShift

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • 4.16.0
    • 4.16
    • Storage / Operators
    • None
    • Important
    • No
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem:

        The azure csi driver operator cannot run in a HyperShift control plane because it has this selector: node-role.kubernetes.io/master: ""  

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

          4.16 ci latest

      How reproducible:

      always    

      Steps to Reproduce:

          1. Install hypershift
          2. Create azure hosted cluster
          

      Actual results:

          azure-disk-csi-driver-operator pod remains in Pending state

      Expected results:

          all control plane pods run

      Additional info:

          

            [OCPBUGS-28765] Azure CSI Driver operator has incorrect node selector for HyperShift

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Critical: OpenShift Container Platform 4.16.0 bug fix and security update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHSA-2024:0041

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Critical: OpenShift Container Platform 4.16.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:0041

            Hi rh-ee-mpatlaso,

            Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            OpenShift Jira Bot added a comment - Hi rh-ee-mpatlaso , Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            Looks like this bug is far enough along in the workflow that a code fix is ready. Customers and support need to know the backport plan. Please complete the "Target Backport Versions" field to indicate which version(s) will receive the fix.

            OpenShift Jira Bot added a comment - Looks like this bug is far enough along in the workflow that a code fix is ready. Customers and support need to know the backport plan. Please complete the " Target Backport Versions " field to indicate which version(s) will receive the fix.

            Cesar Wong added a comment -

            rh-ee-mpatlaso I submitted this PR for this bug: https://github.com/openshift/cluster-storage-operator/pull/448 
            Tested with hypershift and works. Please feel free to close if you are working on your own.

            Cesar Wong added a comment - rh-ee-mpatlaso I submitted this PR for this bug: https://github.com/openshift/cluster-storage-operator/pull/448   Tested with hypershift and works. Please feel free to close if you are working on your own.

              rh-ee-mpatlaso Maxim Patlasov
              cewong@redhat.com Cesar Wong
              Rohit Patil Rohit Patil
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: