This seems to be an issue when you are using https to to interact with the XMLRPC-API:
tyler@i5-ubuntu:~$ lava-tool auth-add *http://* tyler-baker@validation.linaro.org/RPC2/ Paste token for http://tyler-baker@validation.linaro.org/RPC2/: Token added successfully for user tyler-baker.
tyler@i5-ubuntu:~/Dev/LAVA/bootloader-job-def-tests$ lava-tool auth-add * https*://tyler-baker@validation.linaro.org/RPC2/ Paste token for https://tyler-baker@validation.linaro.org/RPC2/: ERROR: Token rejected by server for user tyler-baker.
I just checked post build lava, it's using https.
From another conversation:
On Sat, Aug 17, 2013 at 11:45:35AM +0100, Matthew Hart wrote:
Hi all,
This is now done. HTTP is redirected to HTTPS for staging. I'm wondering if we should do the same thing for control?
Perhaps this change or lack there of is the cause for this issue? I'm going to assign this issue to Matt.
On 17 August 2013 22:17, Fathi Boudra fathi.boudra@linaro.org wrote:
Hi,
On 15 August 2013 12:39, Matt Hart matthew.hart@linaro.org wrote:
Also, validation.linaro.org will be unavailable from Saturday morning to perform some maintenance in the lab. I expect the service to be back Saturday afternoon.
I'm not sure if it's related but CI jobs fails to submit to LAVA: Error making a LAVA request: <ProtocolError for ciadmin:xxx@validation.linaro.org/RPC2/: 401 UNAUTHORIZED>
I opened: https://bugs.launchpad.net/lava-lab/+bug/1213558
afaics, I can submit LAVA jobs with my own account but not with CI.
Cheers, Fathi
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation