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

[release-4.18] Data disks defined in the machine set configuration are not being provisioned onto an Azure Stack Hub

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • None
    • None
    • None
    • In Progress
    • Bug Fix
    • Hide
      Before this update, the Azure machine provider was not passing the `dataDisks` configuration from the `MachineSet` into the virtual machine creation API request for the Azure Stack Hub. As a consequence, new machines were created without the specified data disks because the configuration was silently ignored during the VM creation process. With this release, the VM creation for the Azure Stack Hub is updated to include the `dataDisks` configuration. An additional update manually implements the behavior of the `deletionPolicy: Delete` parameter in the controller because the Azure Stack Hub does not natively support this option. As a result, data disks are correctly provisioned on the Azure Stack Hub VMs. The `Delete` policy is also functionally supported, which ensures that disks are properly removed when their machines are removed.
      Show
      Before this update, the Azure machine provider was not passing the `dataDisks` configuration from the `MachineSet` into the virtual machine creation API request for the Azure Stack Hub. As a consequence, new machines were created without the specified data disks because the configuration was silently ignored during the VM creation process. With this release, the VM creation for the Azure Stack Hub is updated to include the `dataDisks` configuration. An additional update manually implements the behavior of the `deletionPolicy: Delete` parameter in the controller because the Azure Stack Hub does not natively support this option. As a result, data disks are correctly provisioned on the Azure Stack Hub VMs. The `Delete` policy is also functionally supported, which ensures that disks are properly removed when their machines are removed.
    • None
    • None
    • None
    • None

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

      The dataDisks configuration from the MachineSet CRD is silently ignored as it's not passed through to the StorageProfile struct when creating the VirtualMachine. The ask here is for the Azure Machine API Provider to handle the dataDisks configuration on Azure stack in the same way it does on normal Azure.

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

      How reproducible:

       Excerpt from machineset providerSpec:

      providerSpec:
        value:
          apiVersion: machine.openshift.io/v1beta1
          credentialsSecret:
            name: azure-cloud-credentials
            namespace: openshift-machine-api
          dataDisks:
            - deletionPolicy: Delete
              diskSizeGB: 200
              managedDisk:
                storageAccountType: ""
              nameSuffix: data

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

      Expected results:

      Additional info:

      Customer has opened the following PR to start the process of getting this supported in the machine api provider - https://github.com/openshift/machine-api-provider-azure/pull/149

              rmanak@redhat.com Radek Manak
              rhn-support-zekhan Zeba Khan
              None
              None
              Zhaohua Sun Zhaohua Sun
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: