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

Add status check for Azure NIC provisioning

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 4.12, 4.14.z
    • Cloud Compute / Unknown
    • None
    • Moderate
    • None
    • CLOUD Sprint 267, CLOUD Sprint 268
    • 2
    • False
    • Hide

      None

      Show
      None
    • Hide
      Virtual machines on Azure would sometimes failed operations because an attached NIC was in a "ProvisioningFailed" state, yet still operational.

      The controller for Azure machines will now check the provisioning status of a NIC, and attempt to refresh the NIC's state on a regular basis.
      Show
      Virtual machines on Azure would sometimes failed operations because an attached NIC was in a "ProvisioningFailed" state, yet still operational. The controller for Azure machines will now check the provisioning status of a NIC, and attempt to refresh the NIC's state on a regular basis.
    • Bug Fix
    • In Progress

      Description of problem:

      Azure creates a nic in "provisioning failed" and the code is not checking the provisioning status.

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

      4.12

      How reproducible:

      100%

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

      Expected results:

      Additional info:

      https://github.com/openshift/machine-api-provider-azure/blob/main/pkg/cloud/azure/actuators/machine/reconciler.go

https://pkg.go.dev/github.com/Azure/azure-sdk-for-go@v68.0.0+incompatible/services/network/mgmt/2021-02-01/network#InterfacePropertiesFormat

              rh-ee-nbrubake Nolan Brubaker
              rhn-support-vkochuku Vinu Kochukuttan
              Zhaohua Sun Zhaohua Sun
              Votes:
              1 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: