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

[azure] Azure Stack Hub (wwt) UPI installation failed to scale up worker nodes using machinesets

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • Hide
      Cause: machinesets follow the IPI pattern of using "$clusterID-cluster" as the availabilitySet's name, whereas UPI uses "$clusterID-avset"
      Result: Scaling up a compute machineset will fail in AzureStack UPI with:
      Message: failed to create vm $clusterID-worker-mtcazs-2gjsl: failure sending request for machine
      Fix: update the UPI templates to use the correct AvailabilitySet name.
      Show
      Cause: machinesets follow the IPI pattern of using "$clusterID-cluster" as the availabilitySet's name, whereas UPI uses "$clusterID-avset" Result: Scaling up a compute machineset will fail in AzureStack UPI with: Message: failed to create vm $clusterID-worker-mtcazs-2gjsl: failure sending request for machine Fix: update the UPI templates to use the correct AvailabilitySet name.
    • Bug Fix
    • Done

      Description of problem:

      Cannot scale up worker node have deploying OCP 4.12 cluster via UPI on Azure Stack Hub

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

      4.12.0-0.nightly-2022-12-27-111646

      How reproducible:

      Always

      Steps to Reproduce:

      1.Following the step described in the document: https://github.com/openshift/installer/blob/master/docs/user/openstack/install_upi.md create cluster 
      2. in https://github.com/openshift/installer/blob/master/docs/user/openstack/install_upi.md#remove-machines-and-machinesets only control plane machines manifests were removed, worker machines manifests remain untouched.After three masters and three worker nodes were created by ARM templates.
      3. additional worker were added using machine sets via command
      $oc scale  --replicas=1 machineset  maxu-stack0-nsqhm-worker-mtcazs  -n openshift-machine-api
      

      Actual results:

      $oc describe machine  maxu-stack0-nsqhm-worker-mtcazs-2gjsl -n openshift-machine-api
      Message:               failed to create vm maxu-stack0-nsqhm-worker-mtcazs-2gjsl: failure sending request for machine maxu-stack0-nsqhm-worker-mtcazs-2gjsl: cannot create vm: compute.VirtualMachinesClient#CreateOrUpdate: Failure sending request: StatusCode=404 -- Original Error: Code="NotFound" Message="The Availability Set '/subscriptions/de7e09c3-b59a-4c7d-9c77-439c11b92879/resourceGroups/maxu-stack0-nsqhm-rg/providers/Microsoft.Compute/availabilitySets/maxu-stack0-nsqhm-cluster' cannot be found."

      Expected results:

      The installer should be able to create and manage machineset

      Additional info:

      1. https://issues.redhat.com/browse/OCPBUGS-4405
      2. After the following changes of the arm files as the following, resolve this issue.
      "imageName" : "[parameters('baseName')]", 
      "masterAvailabilitySetName" : "[concat(parameters('baseName'), '-cluster')]",

       

            rdossant Rafael Fonseca dos Santos
            maxu@redhat.com May Xu
            May Xu May Xu
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: