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

[CAPI Azure] installer storage account creation failed with long storageAccountName

XMLWordPrintable

    • Critical
    • None
    • Installer (PB) Sprint 258
    • 1
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required
    • Done

      This is a clone of issue OCPBUGS-37953. The following is the description of the original issue:

      Description of problem:

      Specify long cluster name in install-config, 
      ==============
      metadata:
        name: jima05atest123456789test123
      
      Create cluster, installer exited with below error:
      08-05 09:46:12.788  level=info msg=Network infrastructure is ready
      08-05 09:46:12.788  level=debug msg=Creating storage account
      08-05 09:46:13.042  level=debug msg=Collecting applied cluster api manifests...
      08-05 09:46:13.042  level=error msg=failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed provisioning resources after infrastructure ready: error creating storage account jima05atest123456789tsh586sa: PUT https://management.azure.com/subscriptions/53b8f551-f0fc-4bea-8cba-6d1fefd54c8a/resourceGroups/jima05atest123456789t-sh586-rg/providers/Microsoft.Storage/storageAccounts/jima05atest123456789tsh586sa
      08-05 09:46:13.042  level=error msg=--------------------------------------------------------------------------------
      08-05 09:46:13.042  level=error msg=RESPONSE 400: 400 Bad Request
      08-05 09:46:13.043  level=error msg=ERROR CODE: AccountNameInvalid
      08-05 09:46:13.043  level=error msg=--------------------------------------------------------------------------------
      08-05 09:46:13.043  level=error msg={
      08-05 09:46:13.043  level=error msg=  "error": {
      08-05 09:46:13.043  level=error msg=    "code": "AccountNameInvalid",
      08-05 09:46:13.043  level=error msg=    "message": "jima05atest123456789tsh586sa is not a valid storage account name. Storage account name must be between 3 and 24 characters in length and use numbers and lower-case letters only."
      08-05 09:46:13.043  level=error msg=  }
      08-05 09:46:13.043  level=error msg=}
      08-05 09:46:13.043  level=error msg=--------------------------------------------------------------------------------
      08-05 09:46:13.043  level=error
      08-05 09:46:13.043  level=info msg=Shutting down local Cluster API controllers...
      08-05 09:46:13.298  level=info msg=Stopped controller: Cluster API
      08-05 09:46:13.298  level=info msg=Stopped controller: azure infrastructure provider
      08-05 09:46:13.298  level=info msg=Stopped controller: azureaso infrastructure provider
      08-05 09:46:13.298  level=info msg=Shutting down local Cluster API control plane...
      08-05 09:46:15.177  level=info msg=Local Cluster API system has completed operations    
      
      See azure doc[1], the naming rules on storage account name, it must be between 3 and 24 characters in length and may contain numbers and lowercase letters only.
      
      The prefix of storage account created by installer seems changed to use infraID with CAPI-based installation, it's "cluster" when installing with terraform.
      
      Is it possible to change back to use "cluster" as sa prefix to keep consistent with terraform? because there are several storage accounts being created once cluster installation is completed. One is created by installer starting with "cluster", others are created by image-registry starting with "imageregistry". And QE has some CI profiles[2] and automated test cases relying on installer sa, need to search prefix with "cluster", and not sure if customer also has similar scenarios.
      
      [1] https://learn.microsoft.com/en-us/azure/storage/common/storage-account-overview
      [2] https://github.com/openshift/release/blob/master/ci-operator/step-registry/ipi/install/heterogeneous/ipi-install-heterogeneous-commands.sh#L241

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

          

      How reproducible:

          

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

          

      Expected results:

          

      Additional info:

          

            jhixson_redhat John Hixson
            openshift-crt-jira-prow OpenShift Prow Bot
            Jinyun Ma Jinyun Ma
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: