garm-cli credentials?

[SystemKeeper]

So I am still running garm 0.1.3 on one machine and today I was greeted with this:

# garm-cli pool list -a --debug
GET /api/v1/pools HTTP/1.1
Host: garm...
User-Agent: Go-http-client/1.1
Accept: application/json
Authorization: Bearer eyJhbGci....
Accept-Encoding: gzip


HTTP/1.1 401 Unauthorized
Content-Length: 47
Connection: keep-alive
Content-Type: application/json
Date: Fri, 14 Jun 2024 14:09:53 GMT
Server: nginx

{"error":"Authentication failed","details":""}

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x963e10]

goroutine 1 [running]:
github.com/cloudbase/garm/cmd/garm-cli/cmd.glob..func15(0xc000032e00?, {0xc0006568c0?, 0x4?, 0xa8de54?})
	/opt/garm-src/cmd/garm-cli/cmd/pool.go:125 +0x2b0
github.com/spf13/cobra.(*Command).execute(0xfcca60, {0xc0006568a0, 0x2, 0x2})
	/opt/garm-src/vendor/github.com/spf13/cobra/command.go:916 +0x87c
github.com/spf13/cobra.(*Command).ExecuteC(0xfcf2a0)
	/opt/garm-src/vendor/github.com/spf13/cobra/command.go:1044 +0x3a5
github.com/spf13/cobra.(*Command).Execute(...)
	/opt/garm-src/vendor/github.com/spf13/cobra/command.go:968
github.com/cloudbase/garm/cmd/garm-cli/cmd.Execute()
	/opt/garm-src/cmd/garm-cli/cmd/root.go:55 +0x134
main.main()
	/opt/garm-src/cmd/garm-cli/main.go:20 +0xf

Besides the SIGSEGV (which might be fixed already in newer versions), I am wondering how garm-cli determines which credentials to use? garm and garm-cli are the same version.

Not sure how I ended up in this state 😵‍💫

[gabriel-samfira]

This might be fixed in main. You can give the CLI a try. It should work with older GARM servers. Your token may have expired. Run:

garm-cli profile login

to refresh the token. It shouldn't seg fault, obviously 😞

Edit:

Yup. It's fixed in main:

ubuntu@garm:~$ garm-cli pool ls -a
Error: [GET /pools][401] ListPools default {"error":"Authentication failed","details":""}

[SystemKeeper]

Awesome, that worked, thanks a lot! I was not aware of the login command 😅

[gabriel-samfira]

we have a fair number of commands and options. Keeping things simple is more difficult than expected. It's easy for things to get lost.

I will add a proper message when a token expires, with the associated command to refresh it. It;s a JWT so we can see when it expires.