Hey sorry still running into issues. I'm not able ...
# help
u
Hey sorry still running into issues. I'm not able to connect to the actual azure blob storage, this is the console errror:
time="2021-12-06T19:42:13-08:00" level=warning msg="Could not access storage namespace" func="<http://github.com/treeverse/lakefs/pkg/api.(*Controller).CreateRepository|github.com/treeverse/lakefs/pkg/api.(*Controller).CreateRepository>" file="/lakeFS/pkg/api/controller.go:1149" error="write error: -> <http://github.com/Azure/azure-storage-blob-go/azblob.newStorageError|github.com/Azure/azure-storage-blob-go/azblob.newStorageError>, /home/runner/go/pkg/mod/github.com/!azure/azure-storage-blob-go@v0.14.0/azblob/zc_storage_error.go:42\n===== RESPONSE ERROR (ServiceCode=InvalidAuthenticationInfo) =====\nDescription=Authentication information is not given in the correct format. Check the value of Authorization header.\nRequestId:99b65e84-801e-006f-801c-eb4b9a000000\nTime:2021-12-07T03:42:13.7541419Z, Details: \n  Code: InvalidAuthenticationInfo\n  PUT <https://newintelligentsys02sa.blob.core.windows.net/dummy?blockid=6xDVl8JQTja6vlELhJ8MMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA%3D%3D&comp=block&timeout=601>\n  Authorization: REDACTED\n  Content-Length: [70]\n  User-Agent: [Azure-Storage/0.14 (go1.16.2; Windows_NT)]\n  X-Ms-Client-Request-Id: [37f72e80-b2e9-4508-67d0-5242348b5790]\n  X-Ms-Date: [Tue, 07 Dec 2021 03:42:13 GMT]\n  X-Ms-Version: [2020-04-08]\n  --------------------------------------------------------------------------------\n  RESPONSE Status: 400 Authentication information is not given in the correct format. Check the value of Authorization header.\n  Content-Length: [297]\n  Content-Type: [application/xml]\n  Date: [Tue, 07 Dec 2021 03:42:13 GMT]\n  Server: [Microsoft-HTTPAPI/2.0]\n  X-Ms-Error-Code: [InvalidAuthenticationInfo]\n  X-Ms-Request-Id: [99b65e84-801e-006f-801c-eb4b9a000000]\n\n\n" service=api_gateway storage_namespace=<https://newintelligentsys02sa.blob.core.windows.net>
I'm not sure why it's saying the authentication isn't in the correct format. I'm following the format provided here: https://docs.lakefs.io/reference/configuration.html#example-azure-blob-storage, at the end of the console log you can see the format of my storage account name
u
Hey @Yusuf Khan, I'm looking into this, will update here soon
u
Thank you so much, you guys are such an excellent community. I really hope once I get the hang of it I can help contribute rather than only ask questions
u
😊 that would be awesome @Yusuf Khan! Can you please share with me the structure of the Authorization header redacted from the logs? How many parts does it have?
u
@Yusuf Khan, just to make sure - since you mention the format of the storage account name - the storage account name is not exactly the lakeFS storage namespace. A storage account is an account you create in Azure Blob: it contains all your storage data. EDIT: The storage namespace in lakeFS will be the storage container URL. (edited to reflect @Yusuf Khan's result)
u
@Yoni Augarten hey, I figured it out. In the LakeFS UI itself when I was entering the namespace the helper text had the https structure of the storage account but I had to add that plus "/mycontainername" to it and that worked
u
Thanks for the update @Yusuf Khan! Just to make sure, the problem was only in the storage namespace entered? No changes were required in the lakeFS configuration file?
u
In any case we will look into it and make sure the example is more helpful
u
Thanks for the clarification!
u
@Yoni Augarten Augart, en hey its me again sorry, I'm getting 401 unauthorized when running lakectl ingest, looking at the docs I need to be able to list, which I have Storage Account Contributor and Storage Blob Data Contributor. The second thing says the Lakefs installation needs access to read, not sure what that means exactly?
u
First of all let's verify that your lakectl command is properly configured. Can you share the output of
lakectl repo list
?
u
Weird, when I run
lakectl repo list
I also get 401 Unauthorized, but when I did the lakectl ingest --dry-run it listed the blobs at the specified location
u
I'm sorry Yoni. Don't hate me. I saved the config file as "lakctl.yaml" rather than ".lakectl.yaml"
u
I'm sorry 😞, I promise to pay the help forward
u
🙂 no worries! Thanks for the update