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

[Windows VMs] Machine providerID should be consistent with node providerID

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.16, 4.17
    • Windows Containers
    • None
    • Moderate
    • No
    • 3
    • WINC - Sprint 266
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      *Cause*: incorrect RBAC permission for azure-cloud-node-manager
      *Consequence*: azure-cloud-node-manager not running correctly
      *Fix*: Adjust the RBAC with the missing permissions and configure azure-cloud-node-manager to use WICD kubeconfig
      *Result*: azure-cloud-node-manager is able to properly configure the Windows node in Azure with providerID field.
      Show
      *Cause*: incorrect RBAC permission for azure-cloud-node-manager *Consequence*: azure-cloud-node-manager not running correctly *Fix*: Adjust the RBAC with the missing permissions and configure azure-cloud-node-manager to use WICD kubeconfig *Result*: azure-cloud-node-manager is able to properly configure the Windows node in Azure with providerID field.
    • Bug Fix
    • In Progress

      Description of problem:

          Node object does not have the providerId as machine object

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

          4.16.0-0.nightly-2024-07-07-171226

      How reproducible:

          Always

      Steps to Reproduce:

         Run below commands-
 miyadav@miyadav-thinkpadx1carbongen8:~$ oc get nodes windows-6sk78 -o=jsonpath={.spec.providerID}

miyadav@miyadav-thinkpadx1carbongen8:~$ oc get machines windows-6sk78 -o=jsonpath={.spec.providerID}
azure:///subscriptions/53b8f551-f0fc-4bea-8cba-6d1fefd54c8a/resourceGroups/miyadav-0807az-g264k-rg/providers/Microsoft.Compute/virtualMachines/windows-6sk78

      Actual results:

          No probiderID for windows node 
          Expected results: same providerId as machineID in windows node as well

      Additional info:

        this works well for Linux workers 
miyadav@miyadav-thinkpadx1carbongen8:~$ oc get machine miyadav-0807az-g264k-worker-westus-4wlj7 -o=jsonpath={.spec.providerID}
azure:///subscriptions/53b8f551-f0fc-4bea-8cba-6d1fefd54c8a/resourceGroups/miyadav-0807az-g264k-rg/providers/Microsoft.Compute/virtualMachines/miyadav-0807az-g264k-worker-westus-4wlj7

miyadav@miyadav-thinkpadx1carbongen8:~$ oc get nodes  miyadav-0807az-g264k-worker-westus-4wlj7 -o=jsonpath={.spec.providerID}
azure:///subscriptions/53b8f551-f0fc-4bea-8cba-6d1fefd54c8a/resourceGroups/miyadav-0807az-g264k-rg/providers/Microsoft.Compute/virtualMachines/miyadav-0807az-g264k-worker-westus-4wlj7

   
 

       https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-48363

       

      must-gather -https://drive.google.com/file/d/1xBkyWZhHl4GWep2JGvh0WXmQ1txssc-8/view?usp=sharing

       

       

              jvaldes@redhat.com Jose Valdes
              rh-ee-miyadav Milind Yadav
              Weinan Liu Weinan Liu
              Votes:
              1 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: