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

Azure CAPI: installation failed when configured customer-managed key for storage account

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • None
    • 4.17
    • None
    • Moderate
    • None
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, after you creating a private {product-title} cluster on {azure-first}, the installation program did not mark the storage account that it created as private. As a result, the storage account was publically available. With this release, the installation program now correctly always marks the storage account as private regardless if the cluster is publically or privately available. (link:https://issues.redhat.com/browse/OCPBUGS-42349[*OCPBUGS-42349*])
      Show
      * Previously, after you creating a private {product-title} cluster on {azure-first}, the installation program did not mark the storage account that it created as private. As a result, the storage account was publically available. With this release, the installation program now correctly always marks the storage account as private regardless if the cluster is publically or privately available. (link: https://issues.redhat.com/browse/OCPBUGS-42349 [* OCPBUGS-42349 *])
    • Bug Fix
    • Done

      Description of problem:

      On 4.17 rc.3/rc.5, install cluster with customer-managed key for storage account configured will fail.
      
      install-config:
      =======
      platform:
        azure:
          customerManagedKey:
            keyVault:
              keyName: ci-op-b7b9151w-eca8b-key
              name: ci-op-b7b9151w-eca8b-kv
              resourceGroup: ci-op-b7b9151w-eca8b-rg
            userAssignedIdentityKey: ci-op-b7b9151w-eca8b-identity
      
      Error
      ========  
      level=info msg=Waiting up to 15m0s (until 7:01PM UTC) for network infrastructure to become ready...
      level=info msg=Network infrastructure is ready
      level=error msg=failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed provisioning resources after infrastructure ready: failed to create blob container vhd: PUT https://management.azure.com/subscriptions/53b8f551-f0fc-4bea-8cba-6d1fefd54c8a/resourceGroups/ci-op-b7b9151w-eca8b-95g9d-rg/providers/Microsoft.Storage/storageAccounts/ciopb7b9151weca8b95g9dsa/blobServices/default/containers/vhd
      level=error msg=--------------------------------------------------------------------------------
      level=error msg=RESPONSE 400: 400 Bad Request
      level=error msg=ERROR CODE: UnsupportedHeader
      level=error msg=--------------------------------------------------------------------------------
      level=error msg={
      level=error msg=  "error": {
      level=error msg=    "code": "UnsupportedHeader",
      level=error msg=    "message": "One of the headers specified in the request is not supported.\nRequestId:7ca1ed39-d01c-0107-6f20-0d5e97000000\nTime:2024-09-22T18:49:25.9448932Z"
      level=error msg=  }
      level=error msg=}
      level=error msg=--------------------------------------------------------------------------------
      level=error
      level=info msg=Shutting down local Cluster API controllers...
      level=info msg=Stopped controller: Cluster API
      level=info msg=Stopped controller: azure infrastructure provider
      level=info msg=Stopped controller: azureaso infrastructure provider
      level=info msg=Shutting down local Cluster API control plane...
      level=info msg=Local Cluster API system has completed operations
      Installer exit with code 4

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

      4.17.0-rc.3/4.17.0-rc.5 

      How reproducible:

      Always    

      Steps to Reproduce:

          1. set customerManagedKey in install-config
          2. create cluster
          3.
          

      Actual results:

          installation failed

      Expected results:

          installation succeeded.

      Additional info:

      Issue is introduced by https://github.com/openshift/installer/pull/8984 to fix bug https://issues.redhat.com/browse/OCPBUGS-41542.
      https://github.com/openshift/installer/pull/9006 is the fix for this issue and already merged, but not included in 4.17.0-rc.3/4.17.0-rc.5.
      
      The purpose of this bug is to add known issue in 4.17 RN, and the fix will be in the following 4.17.1 z-stream.     

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

                Created:
                Updated:
                Resolved: