Hi team , while setting up lakectl i am getting this error, even if i configured the .yaml file with access key and secret key.

Hey @setu suyagya ! Sorry to hear that. Mind sharing the configuration file (make sure to change the credentials to blank) and its path?

Also, are these credentials for a user that has permissions to list users?

are you able to login to lakefs webui?

yes

and do you see this access key set for the relevant user?

what about the permissions? are you able to list users through the UI?

well, it seems like the user should have permissions to list users... I wasn't able to reproduce it

$ lakectl auth users list
+----------------+-------------------------------+
| USER ID        | CREATION DATE                 |
+----------------+-------------------------------+
| Or Tzabary     | 2022-08-04 11:48:14 +0300 IDT |
+----------------+-------------------------------+

which lakeFS version are you running?

and how did you run lakefs? using the everything bagel docker-compose file?

i pulled the docker image using curl https://compose.lakefs.io |docker-compose -f - up and the from docker terminal and web ui

alright, let me try to reproduce it using this method

works...

where are you running the

lakectl auth users list

command from? within the docker container or from your terminal?

aha... well, the container doesn't have the .lakectl.yaml configuration file

when you ran the

lakectl config

, was that from within that terminal? or your own?

from this same terminal from docker

it still works for me. can you please re-run the

lakectl config

and provide the credentials again? if you don't have them, you can just generate another set of access/secret key and use them instead

my current assumption is that the secret is not configured properly

but still same error

do you mind doing it on a new set of credentials?

ya ok let me try

still same

🤔 interesting... let me see what else we can do

any logs for the lakefs instance reporting these failed auth requests?

i guess its not writing the user credential in yaml file properly

it looks like it

because if it would've been an issue with the access key, you'd get a different error message

if you run

cat ~/.lakectl.yaml

, does it look like the credentials you've set?

(from within the container)

details stored correctly

may I suggest we'll go on a quick call to try and troubleshoot this together?

ya sure

summarizing our call here; we created another set of credentials, configured them through

lakefs config

and it worked.

Thanks for you quick call help.

sure, happy to assist. enjoy lakeFSing 🙂

hey @setu suyagya, how is it going? I wonder if you encountered any further issues, or you have any questions

yes, how can i setup glue metastore in lakectl file

well, it's supported and part of lakefs' configuration (not lakectl as it's the cli interface to lakefs) you can read more on how to set it up in our docs

i read this, getting stuck that how to add the required details in lakectl.yaml file

I'm sorry, I was mistaken

it's part of the lakectl.yaml configuration

where are you stuck at?

I'm not sure I follow on the problem. you're missing the file location? the values you should be using? or the text editor itself?

you should be using this interface either with Hive or Glue configuration, not both

if it's hive, the configuration should look like:

metastore:
  type: hive
  hive:
    uri: hive-metastore:9083

if it's glue, the configuration should like look:

metastore:
  type: glue
  glue:
    catalog-id: 123456789012
    region: us-east-1
    profile: default # optional, implies using a credentials file
    credentials:
      access_key_id: AKIAIOSFODNN7EXAMPLE
      secret_access_key: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY

yes , i just want to add glue configuration in yaml ile

file*

ok, so its configuration requires the catalog id, region it operates in, and AWS credentials to access the catalog

is it working with only aws credential, or with local glue image in docker

is there any command through which i can open the lakectl.yaml file in texteditor mode

is it working with only aws credential, or with local glue image in docker

well, I'm not sure it's supported by AWS to run Glue without any credentials reference (see here)

is there any command through which i can open the lakectl.yaml file in texteditor mode

you can use

nano

or

vi

(more advanced & complex). if you're using the docker-compose (everything bagel) for instance, you can either use environment variables to override the configuration file, or mount a docker volume with the configuration file and edit it in your host.

Thanks for these, I am trying to setup accordingly if anything goes wrong will ping again.