Hi experts,
It's error when I auth token with the lava-too, because my I deploy the lava 2017.7 with SSL Self-signed certificate. Now I can use the XML-RPC to auth the token with " ssl._create_unverified_context ". How can I do ? I want use the lava-tool .
import ssl
ssl._create_default_https_context = ssl._create_unverified_context
import xmlrpclib
username = "lavaadmin"
token = "onku07n16r2uktjz40otgn0n9m7q1bp1b75dr4u0ph0juy7jnb8csi0u9x7fg3sf1mpgnxw00sq1otmzl3rqpdu4tl5fam45m5xyt25oin020ohkajzrx7ze0aaukkdt"
hostname = "autotest001"
protocol = "https" # http or preferably https
server = xmlrpclib.ServerProxy("%s://%s:%s@%s/RPC2" % (protocol, username, token, hostname))
device_hostname = "qemu_test01"
jinjia_string = " {% extends 'qemu.jinja2' %} {% set mac_addr = '52:54:00:12:34:60' %} {% set memory = '1024' %} "
> lava-tool auth-add --token-file /home/lavaadmin/xuhy/qemu_test_token https://1680141@10.5.21.5/RPC2
>
> ERROR: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate
> verify failed (_ssl.c:661)>
Best Regards
XuHongyu
-----Original Message-----
From: Xu, Hongyu
Sent: 2017年9月12日 14:47
To: 'Neil Williams' <neil.williams(a)linaro.org>
Cc: Lava-users(a)lists.linaro.org
Subject: RE: [Lava-users] auth token
We deploy the lava on the Internal lan, an the domain names is private . But let's Encrypt can only issue certificates for valid public domain names. Are there any other Suggestions?
Best Regards
XuHongyu
-----Original Message-----
From: Neil Williams [mailto:neil.williams@linaro.org]
Sent: 2017年9月11日 15:35
To: Xu, Hongyu <hongyu.xu(a)hxt-semitech.com>
Cc: Lava-users(a)lists.linaro.org
Subject: Re: [Lava-users] auth token
On 11 September 2017 at 08:28, Xu, Hongyu <hongyu.xu(a)hxt-semitech.com> wrote:
> Hi lava experts:
>
>
>
> I deploy the lava 2017.7 with SSL Self-signed certificate, then I
> want to create the device-dictionary for the qemu devices, it’s error
> when I add auth_token. Please give me some suggest!
>
>
That needs to be fixed within your own SSL configuration. Lots of security packages have issues with self-signed certificates, so it is better to look at solutions like letsencrypt. Details of how this is configured are outside the scope of the lava-users mailing list, it's a general system admin task and a variety of guides are available online.
>
> lava-tool auth-add --token-file /home/lavaadmin/xuhy/qemu_test_token
> --user-shortcut 1680141 --endpoint-shortcut qemu_test01
> https://1680141@10.5.21.5
>
> ERROR: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate
> verify failed (_ssl.c:661)>
>
>
>
> Best Regards
>
>
>
> XuHongyu
>
>
>
> From: Xu, Hongyu
> Sent: 2017年9月4日 14:41
> To: 'Lava-users(a)lists.linaro.org' <Lava-users(a)lists.linaro.org>
> Subject: Local Django user accounts
>
>
>
>
>
> Hi all,
>
>
>
> I have installed the lava-serer (2017.7) on my DEBIAN 9.10. But now
> I can’t sign in with the local Django user, this is the error infomations:
>
> Forbidden (403)
>
> CSRF verification failed. Request aborted.
>
> You are seeing this message because this site requires a CSRF cookie
> when submitting forms. This cookie is required for security reasons,
> to ensure that your browser is not being hijacked by third parties.
>
> If you have configured your browser to disable cookies, please
> re-enable them, at least for this site, or for 'same-origin' requests.
>
> More information is available with DEBUG=True.
>
>
This is already covered in the documentation, it's a Django change. If you have tried to solve this by using a self-signed certificate on localhost, you should avoid trying to create https://localhost/ and just update the security settings:
https://staging.validation.linaro.org/static/docs/v2/pipeline-debug.html?hi…
>
> Please give me some advices!
>
>
>
> root@hxtcorp:~# dpkg-query -l lava*
>
> Desired=Unknown/Install/Remove/Purge/Hold
>
> |
> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Tri
> g-pend
>
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
>
> ||/ Name Version Architecture
> Description
>
> +++-=================================-=====================-==========
> +++===========-=======================================================
> +++================
>
> ii lava-coordinator 0.1.7-1 all
> LAVA Coordinator daemon
>
> un lava-dashboard <none> <none>
> (no description available)
>
> un lava-dashboard-tool <none> <none>
> (no description available)
>
> ii lava-dispatcher 2017.7-1~bpo9+1 amd64
> Linaro Automated Validation Architecture dispatcher
>
> un lava-scheduler <none> <none>
> (no description available)
>
> un lava-scheduler-tool <none> <none>
> (no description available)
>
> ii lava-server 2017.7-1~bpo9+1 all
> Linaro Automated Validation Architecture server
>
> ii lava-server-doc 2017.7-1~bpo9+1 all
> Linaro Automated Validation Architecture documentation
>
> ii lava-tool 0.21-1 all
> command line utility for LAVA
>
> un lavapdu <none> <none>
> (no description available)
>
> ii lavapdu-client 0.0.5-1 all
> LAVA PDU client
>
> ii lavapdu-daemon 0.0.5-1 all
> LAVA PDU control daemon
>
>
>
> add the local Django user:
>
> sudo lava-server manage createsuperuser --username $USERNAME
> --email=$EMAIL
>
> sudo lava-server manage authorize_superuser --username $USERNAME
>
>
>
> root@hxtcorp:/etc/lava-server# lava-server manage users list
>
> List of users:
>
> * 1680077
>
> * 1680141
>
> * lava-health
>
> * xuhy
>
>
>
> Best Regards
>
>
>
> XuHongyu
>
>
>
>
>
>
> This email is intended only for the named addressee. It may contain
> information that is confidential/private, legally privileged, or
> copyright-protected, and you should handle it accordingly. If you are
> not the intended recipient, you do not have legal rights to retain,
> copy, or distribute this email or its contents, and should promptly
> delete the email and all electronic copies in your system; do not retain copies in any media.
> If you have received this email in error, please notify the sender promptly.
> Thank you.
>
>
>
>
> _______________________________________________
> Lava-users mailing list
> Lava-users(a)lists.linaro.org
> https://lists.linaro.org/mailman/listinfo/lava-users
>
--
Neil Williams
=============
neil.williams(a)linaro.org
http://www.linux.codehelp.co.uk/
This email is intended only for the named addressee. It may contain information that is confidential/private, legally privileged, or copyright-protected, and you should handle it accordingly. If you are not the intended recipient, you do not have legal rights to retain, copy, or distribute this email or its contents, and should promptly delete the email and all electronic copies in your system; do not retain copies in any media. If you have received this email in error, please notify the sender promptly. Thank you.
Hi，Neil：
I want to control device power on/off by lavapdu.,but when I run pduclient --daemon autotest001 --hostname 10.5.142.6 --command off --port 10
ERROR : Error sending command, wrong daemon hostname?
Can you help me solve this problem?
Lava-server :IP 10.5.21.5 autotest001
Pdudaemon run on the lava-server
Lavapdu.conf:
{
"daemon": {
"hostname": "10.5.21.5",
"port": 16421,
"dbhost": "127.0.0.1",
"dbuser": "pdudaemon",
"dbpass": "pdudaemon",
"dbname": "lavapdu",
"retries": 5,
"logging_level": "INFO"
},
"pdus": {
"192.168.10.2": {
"driver": "apc9210"
},
"192.168.10.3": {
"driver": "apc7952",
"telnetport": 5023
},
"192.168.10.4": {
"driver": "apc7952"
},
"192.168.10.5": {
"driver": "apc8959",
"this": "that",
"something": "else"
},
"192.168.25.52": {
"driver": "apc7952"
}
}
This email is intended only for the named addressee. It may contain information that is confidential/private, legally privileged, or copyright-protected, and you should handle it accordingly. If you are not the intended recipient, you do not have legal rights to retain, copy, or distribute this email or its contents, and should promptly delete the email and all electronic copies in your system; do not retain copies in any media. If you have received this email in error, please notify the sender promptly. Thank you.
Hi lava experts:
I deploy the lava 2017.7 with SSL Self-signed certificate, then I want to create the device-dictionary for the qemu devices, it’s error when I add auth_token. Please give me some suggest!
lava-tool auth-add --token-file /home/lavaadmin/xuhy/qemu_test_token --user-shortcut 1680141 --endpoint-shortcut qemu_test01 https://1680141@10.5.21.5
ERROR: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)>
Best Regards
XuHongyu
From: Xu, Hongyu
Sent: 2017年9月4日 14:41
To: 'Lava-users(a)lists.linaro.org' <Lava-users(a)lists.linaro.org>
Subject: Local Django user accounts
Hi all,
I have installed the lava-serer (2017.7) on my DEBIAN 9.10. But now I can’t sign in with the local Django user, this is the error infomations:
Forbidden (403)
CSRF verification failed. Request aborted.
You are seeing this message because this site requires a CSRF cookie when submitting forms. This cookie is required for security reasons, to ensure that your browser is not being hijacked by third parties.
If you have configured your browser to disable cookies, please re-enable them, at least for this site, or for 'same-origin' requests.
More information is available with DEBUG=True.
Please give me some advices!
root@hxtcorp:~# dpkg-query -l lava*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=================================-=====================-=====================-=======================================================================
ii lava-coordinator 0.1.7-1 all LAVA Coordinator daemon
un lava-dashboard <none> <none> (no description available)
un lava-dashboard-tool <none> <none> (no description available)
ii lava-dispatcher 2017.7-1~bpo9+1 amd64 Linaro Automated Validation Architecture dispatcher
un lava-scheduler <none> <none> (no description available)
un lava-scheduler-tool <none> <none> (no description available)
ii lava-server 2017.7-1~bpo9+1 all Linaro Automated Validation Architecture server
ii lava-server-doc 2017.7-1~bpo9+1 all Linaro Automated Validation Architecture documentation
ii lava-tool 0.21-1 all command line utility for LAVA
un lavapdu <none> <none> (no description available)
ii lavapdu-client 0.0.5-1 all LAVA PDU client
ii lavapdu-daemon 0.0.5-1 all LAVA PDU control daemon
add the local Django user:
sudo lava-server manage createsuperuser --username $USERNAME --email=$EMAIL
sudo lava-server manage authorize_superuser --username $USERNAME
root@hxtcorp:/etc/lava-server# lava-server manage users list
List of users:
* 1680077
* 1680141
* lava-health
* xuhy
Best Regards
XuHongyu
This email is intended only for the named addressee. It may contain information that is confidential/private, legally privileged, or copyright-protected, and you should handle it accordingly. If you are not the intended recipient, you do not have legal rights to retain, copy, or distribute this email or its contents, and should promptly delete the email and all electronic copies in your system; do not retain copies in any media. If you have received this email in error, please notify the sender promptly. Thank you.
Hi,
I upgraded to LAVA 2017.7 (for now I'm using https://github.com/kernelci/lava-docker) and
managed to add my device-type and device as follows:
# Note: I didn't know how to update to 2017.9
docker# lava-server manage device-types add renesas-iwg20m
docker# lava-server manage devices add --device-type renesas-iwg20m --worker lava-docker iwg20m01
However, when I want to add the device dictionary I get an error.
# Note: I am following https://validation.linaro.org/static/docs/v2/pipeline-admin.html
First, I tried with "lava-server manage device-dictionary" as in the documentation, but I failed:
docker# lava-server manage device-dictionary
Unknown command: 'device-dictionary'
Is this only available in the 2017.9 version?
Then, I tried with " lava-tool device-dictionary localhost lava-docker --update myiwg20m.jinja2" but I
get:
Updating device dictionary for lava-docker on localhost
ERROR: Endpoint URL not found in the authorization list: localhost
[Note] my lava-tool is version 0.23-1 (the newest according to apt)
Now, there is a section saying "Using the command line
The device dictionary exists as a jinja2 file in /etc/lava-server/dispatcher-config/devices and can be updated by admins with the necessary access.".
Is this equivalent to using lava-server o lava-tool to install a device dictionary??
Others:
- I confirmed that Pipeline device? is checked.
- Django administration > Devices: what is the meaning of Hostname? I have a value of iwg20m01 (the name of the device),
there is no relation with the server/container's hostname, is there?
- There is an authentication token for the user 'kernel-ci'
Thanks,
Daniel
Hello,
My question looks pretty silly, but as Lava has a big set of features that I haven't discovered yet, I dare ask.
Lava is designed for automatic testing. But everything cannot be fully automated, at least in a reasonable development time frame. More precisely, tests execution can be automated, but the test result needs to be given by a tester. This will happen for example in display or graphics tests.
So, is there a simple way in Lava to let a tester give a manual test result, during or after the test execution? I already have in mind pretty complicated solutions based on Multinode, but simple is key here
Thanks,
Denis
Hi everyone,
As many of you may know, LAVA V2 has been in development and is now ready to roll out across all instances, and we have started this transition with most micro-instances now being predominantly V2.
That leaves the main production instance, validation.linaro.org. Of the supported device types in V2 16 of the 21 have been fully switched over already. Most of these devices can accept V1 and V2 job submissions, but for underlying structural reasons some device types can *only* be V1 or V2, not both.
This is to let you know that in the week following SFO17 we will be switching those devices (HiKey, Drangboard 410c, X15, IFC6410 and Mustang) to V2 only, and any job submissions that are in the old JSON format will be rejected by the LAVA scheduler. If you have bots that submit V1 jobs to those device types, or if you manually submit V1 jobs to those device types, you are strongly urged to switch those off and move to V2 submissions.
The next release of LAVA software will not support V1 at all, so for anyone submitting V1 jobs to *any* device, you will need to move to V2 by the beginning of November at the latest.
Many thanks
Dave
----------------
Dave Pigott
LAVA Lab Lead
Linaro Ltd
t: (+44) (0) 1223 400063
Hello Lava team,
I am trying to test a flashed board that does'nt require to upload tests images ( uImage dtb, rootfs).
The images have been previously flashed on the board under test, by an external Flasher.
To do that, I am using the boot method "minimal" that we have been using for other cases.
In my test, I power on the board, and wait for the kernel prompt ("root@").
When I got the prompt, LAVA try to mount the test partition (previously prepared in deploy phase),
but it fails. I get the following message "No connection retrieved from namespace data".
* Is it possible to do this operation with the boot method "minimal" ?
* Do you have jobs example that do the same operations ?
Find below the boot and test phase I am using :
( In the deploy phase, I have downloaded images that I don't use. )
- boot:
method: minimal
failure_retry: 2
prompts:
- 'root@'
timeout:
minutes: 2
- test:
timeout:
minutes: 5
namespace: flash_to_sd
definitions:
- from: git
repository: /local/dev/frq93151/dispatcher/lava-tests
path: tests-def/ddr_test_definition.yaml
name: ddr_tests
BR
Philippe
Hi all,
I have installed the lava-serer (2017.7) on my DEBIAN 9.10. But now I can't sign in with the local Django user, this is the error infomations:
Forbidden (403)
CSRF verification failed. Request aborted.
You are seeing this message because this site requires a CSRF cookie when submitting forms. This cookie is required for security reasons, to ensure that your browser is not being hijacked by third parties.
If you have configured your browser to disable cookies, please re-enable them, at least for this site, or for 'same-origin' requests.
More information is available with DEBUG=True.
Please give me some advices!
root@hxtcorp:~# dpkg-query -l lava*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=================================-=====================-=====================-=======================================================================
ii lava-coordinator 0.1.7-1 all LAVA Coordinator daemon
un lava-dashboard <none> <none> (no description available)
un lava-dashboard-tool <none> <none> (no description available)
ii lava-dispatcher 2017.7-1~bpo9+1 amd64 Linaro Automated Validation Architecture dispatcher
un lava-scheduler <none> <none> (no description available)
un lava-scheduler-tool <none> <none> (no description available)
ii lava-server 2017.7-1~bpo9+1 all Linaro Automated Validation Architecture server
ii lava-server-doc 2017.7-1~bpo9+1 all Linaro Automated Validation Architecture documentation
ii lava-tool 0.21-1 all command line utility for LAVA
un lavapdu <none> <none> (no description available)
ii lavapdu-client 0.0.5-1 all LAVA PDU client
ii lavapdu-daemon 0.0.5-1 all LAVA PDU control daemon
add the local Django user:
sudo lava-server manage createsuperuser --username $USERNAME --email=$EMAIL
sudo lava-server manage authorize_superuser --username $USERNAME
root@hxtcorp:/etc/lava-server# lava-server manage users list
List of users:
* 1680077
* 1680141
* lava-health
* xuhy
Best Regards
XuHongyu
This email is intended only for the named addressee. It may contain information that is confidential/private, legally privileged, or copyright-protected, and you should handle it accordingly. If you are not the intended recipient, you do not have legal rights to retain, copy, or distribute this email or its contents, and should promptly delete the email and all electronic copies in your system; do not retain copies in any media. If you have received this email in error, please notify the sender promptly. Thank you.
