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

[CAPI] unable to create multi clusters simultaneously on the same host

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.17
    • None
    • Important
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * When installing multiple clusters on {azure-full}, running multiple installations simultaneously from the same installation host will result in only one of the clusters installing successfully. If you run the installations sequentially rather than simultaneously, you can install multiple clusters on {azure-short} from the same installation host. (link:https://issues.redhat.com/browse/OCPBUGS-36202[*OCPBUGS-36202*])
      Show
      * When installing multiple clusters on {azure-full}, running multiple installations simultaneously from the same installation host will result in only one of the clusters installing successfully. If you run the installations sequentially rather than simultaneously, you can install multiple clusters on {azure-short} from the same installation host. (link: https://issues.redhat.com/browse/OCPBUGS-36202 [* OCPBUGS-36202 *])
    • Known Issue
    • Done

      Description of problem:

      Trigger multi clusters installation simultaneously on the same host (same results whether using same user or different users), only the first cluster is succeeded to be installed finally, others are failed with below error and installer exited.
      
      INFO Creating infrastructure resources...         
      INFO Started local control plane with envtest     
      INFO Stored kubeconfig for envtest in: /home/fedora/temp/4.17.0-0.nightly-2024-06-23-145410/ipi-azure-3/.clusterapi_output/envtest.kubeconfig 
      INFO Running process: Cluster API with args [-v=2 --diagnostics-address=0 --health-addr=127.0.0.1:42883 --webhook-port=35065 --webhook-cert-dir=/tmp/envtest-serving-certs-2653017464 --kubeconfig=/home/fedora/temp/4.17.0-0.nightly-2024-06-23-145410/ipi-azure-3/.clusterapi_output/envtest.kubeconfig] 
      INFO Running process: azure infrastructure provider with args [-v=2 --health-addr=127.0.0.1:37009 --webhook-port=35725 --webhook-cert-dir=/tmp/envtest-serving-certs-1415942273 --feature-gates=MachinePool=false --kubeconfig=/home/fedora/temp/4.17.0-0.nightly-2024-06-23-145410/ipi-azure-3/.clusterapi_output/envtest.kubeconfig] 
      INFO Running process: azureaso infrastructure provider with args [-v=0 -metrics-addr=0 -health-addr=127.0.0.1:42173 -webhook-port=44275 -webhook-cert-dir=/tmp/envtest-serving-certs-4070016424 -crd-pattern= -crd-management=none] 
      INFO Created manifest *v1.Namespace, namespace= name=openshift-cluster-api-guests 
      INFO Created manifest *v1.Namespace, namespace= name=capz-system 
      INFO Created manifest *v1.Secret, namespace=openshift-cluster-api-guests name=jimaaz03-n5kfl-azure-client-secret 
      ERROR failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to create infrastructure manifest: Internal error occurred: failed calling webhook "validation.azureclusteridentity.infrastructure.cluster.x-k8s.io": failed to call webhook: Post "https://127.0.0.1:35725/validate-infrastructure-cluster-x-k8s-io-v1beta1-azureclusteridentity?timeout=10s": dial tcp 127.0.0.1:35725: connect: connection refused 
      INFO Shutting down local Cluster API control plane... 
      INFO Stopped controller: Cluster API              
      WARNING process cluster-api-provider-azure exited with error: exit status 1 
      INFO Stopped controller: azure infrastructure provider 
      INFO Stopped controller: azureaso infrastructure provider 
      INFO Local Cluster API system has completed operations      

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

          4.17.0-0.nightly-2024-06-23-145410

      How reproducible:

          Always

      Steps to Reproduce:

          1. Run multi cluster installation on azure platform using CAPI
          2.
          3.
          

      Actual results:

          Only the first cluster is installed successfully, others are failed.

      Expected results:

          All clusters should be installed successfully.

      Additional info:

          

       

              sdasu@redhat.com Sandhya Dasu
              jinyunma Jinyun Ma
              Jinyun Ma Jinyun Ma
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: