lava-tool keyring backend fails on ec2/headless
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
LAVA Tool |
Invalid
|
High
|
Michael Hudson-Doyle |
Bug Description
I tried submitting the job to lava using the following steps.
1) Added the authentication token to a local file ex: token_file_
2) Added the following details into the keyringrc.cfg file as this is needed as a workaround for bug 917570
[backend]
default-
keyring-
3) Used auth-add to one time authenticate using the following command:
lava-tool auth-add --token-file token_file_
4) But, when I do a submit-job I get the following error:
lava-tool submit-job http://<email address hidden>
EXPERIMENTAL - SUBJECT TO CHANGE (See --experimental-
Traceback (most recent call last):
File "/usr/bin/
load_
File "/usr/lib/
run_
File "/usr/lib/
raise SystemExit(
File "/usr/lib/
return command.invoke()
File "/usr/lib/
server.
File "/usr/lib/
return self.__
File "/usr/lib/
verbose=
File "/usr/lib/
headers
xmlrpclib.
This error occurs with both http/https protocol.
But, when I use the token in the submit-job, the command works
for ex: lava-tool submit-job http://
Thanks!!!
Deepti.
As hrw pointed out in another report, we need to distinguish in the
errors somehow why you're getting the 401 response: is it because there
was a username and no token, or a username and an invalid token?