Share via

failed to initialize new pipeline [failed to authenticate credentials for azstorage]

Gyan Prakash Rai 25 Reputation points
2024-10-18T11:02:56.1066667+00:00
  1. I have created a storage account (StorageV2 (general purpose v2)) and a container inside it.
  2. This storage account have both .blob.core.windows.net/ and .dfs.core.windows.net/ private end points. Public Network access is disabled.
  3. Access Key authentication is being used.
  4. Created a PV for this storage account and PVC by using blob.csi.azure.com storage class driver.
  5. Created a deployment to deploy the pod attaching the PVC.

Now, when deploying the Pod, it unable to find the container and cannot mount the given mount path. Ending up giving the below error.

Can someone advise me if I missing any steps or something additional need to be done?

Error:

E1018 09:22:28.758428 9874 nodeserver.go:412] rpc error: code = Internal desc = Mount failed with error: rpc error: code = Unknown desc = exit status 1

Error: failed to initialize new pipeline [failed to authenticate credentials for azstorage] , output:

Please refer to http://aka.ms/blobmounterror for possible causes and solutions for mount errors.

Azure Storage
Azure Storage
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
3,542 questions
Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
3,201 questions
Azure Kubernetes Service
Azure Kubernetes Service
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
2,458 questions
Accepted answer
  1. Prrudram-MSFT 28,286 Reputation points Microsoft Employee Moderator
    2024-10-28T10:20:12.94+00:00

    Hi @Gyan Prakash Rai

    I am glad to know it resolved the issue. I am posting this as answer as it resolved your issue. Please consider accepting this as answer.

    Explanation: AZURE_STORAGE_BLOB_ENDPOINT: Specifies the blob endpoint to use. Defaults to *.blob.core.windows.net, but is useful for targeting storage emulators.
    You can verify if the mount will work on the agent node by running these commands to check if the storage account name, key, and container name are correct. If any of these details are incorrect, the blobfuse mount will not be successful.

    You can find more detailed information about blobfuse environment variables at https://github.com/Azure/azure-storage-fuse#environment-variables.

    Issue : Failed to initialize new pipeline [failed to authenticate credentials for azstorage
    **Error:**E1018 09:22:28.758428 9874 nodeserver.go:412] rpc error: code = Internal desc = Mount failed with error: rpc error: code = Unknown desc = exit status 1

    Error: failed to initialize new pipeline [failed to authenticate credentials for azstorage] , output: Please refer to [http://aka.ms/blobmounterror](https://learn.microsoft.com/en-us/answers/questions/2106317/failed-to-initialize-new-pipeline-(failed-to-authe) for possible causes and solutions for mount errors.

    Solution: You could follow guide here to narrow down the issue: blob-csi-driver/docs/csi-debug.md at master · kubernetes-sigs/blob-csi-driver

    If I have answered your question, please accept this as answer as a token of appreciation.

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Gyan Prakash Rai 25 Reputation points
    2024-10-22T04:47:13.17+00:00

    @Sumarigo-MSFT Thanks for the response.

    • Can you please share the screenshot of the error message? --> Due to restrictions from company I cannot share the whole log. But the error is same, after performing all the steps. Additionally I gave workload identity and user managed identity access to storage account.
    • Based on your issue you're encountering with mounting the Azure Blob storage using the CSI driver in your Kubernetes deployment. Kindly let me know if I'm incorrect. --> yes, that is right
    • Make sure you are using the correct access key for the storage account, and it hasn't expired or been regenerated. Verify the credentials that your deployment is using match those for the storage account. --> I tried with access key and without access key as well ( in this case it uses cluster identity)
    • Ensure that you are using the appropriate endpoint (blob or dfs) based on the type of file system or blob service you're trying to mount. --> Yes, blob end point is being used.
    • Sometimes, network issues can cause authentication failures. Verify that your network connection is stable and that there are no firewall rules blocking access to Azure Storage. --> Network is not an issue here

    I tried the given links, but they are not solving my problem. Issue is coming during the pod creation. Container is not coming up.

    ContainersNotInitialized containers with incomplete status: [istio-init]

    Happy to work with you on this issue.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.