vibhansa-msft
commented
1 year ago You config looks fine to me. You are using key as the credential to authenticate with azure -storage which shall be fine. If it's a HNS account add "type: adls" to "azstorage" section in your config file. Also, you can skip defining "endpoint" if storage account is not behind a private endpoint. As per error logs, its saying "you are not authorized to perform this operation". Kindly check your credentials and if possible validate the connection is going through without blobfuse, like using azcli or some other means just to validate authenticate is pass.
jmjclaessen
Which version of blobfuse was used?
Blobfuse2 2.0.1
Which OS distribution and version are you using?
Red Hat Enterprise Linux 8.4, Linux 4.18.0-305.72.1.el8_4.x86_64
If relevant, please share your mount command.
blobfuse2 mount /blob/sftp/carlo --config-file=/blob/config/config.yaml
What was the issue encountered?
Customers are using sftp for blobstorage to put files on blobstorage. We want to map this blobstorage so we can process the files on it using blobfuse2. Attached the config.yaml file. sftp for blobstorage uses an Azure Datalake V2 account. If i map the drive using account type block drive is mapped but i cannot see the folder stucture. If i only change the type to adls (because this is a hierarchical namespace) i get an authentication error: LOG_ERR [mount.go (368)]: mount : failed to initialize new pipeline [failed to authenticate credentials for azstorage. Only change made is the change from type : block to type: adls
Have you found a mitigation/solution?
No
Please share logs if available.
config yaml.txt blobfuse2 mount error.txt blobfuse command.txt