lava-users February 2021

lava-users@lists.lavasoftware.org

8 participants
13 discussions

by koti

Hi, My test job .yaml does not provide any error while health-check trigger from GUI and give error while submitting the same test job from the command line . you can find the command line submission error as mentioned below. " lavamaster@lava$lavacli -i admin@validation jobs submit /tmp/test.yaml Unable to submit /tmp/target.yaml: <Fault 400: "Problem with submitted job data: expected str for dictionary value @ data['actions'][0]['boot']['parameters']['shutdown-message']">" " I have reported same type of bug for "soft-reboot" command support and provided the patch by lava-team for this soft-reboot support issue i.e " https://git.lavasoftware.org/lava/lava/-/merge_requests/1067/diffs#05da71b3… " Can someone provide the path for "shutdown-message" support also? Regards, Koti

3 years

What count in multinode mean?

by cnspring2002

Hello, I have a question about "count" in lava multinode, for next: lava-multinode: roles: device: count: 2 device_type: xxx What does "count" mean? I know the job will only be scheduled if there are 2 "xxx" based device idle. But, after that, how I could use one device do one task, and use another device to do another task? How can I assign different tasks to the 2 devices with the same devicetype? E.g. device xxx1 based on xxx device xxx2 based on xxx Then xxx1 run "ls" while xxx2 run "uname"?

4 years, 1 month

Job error: Invalid job data: ['Device not configured to support serial connection.', 'Device not configured to support serial connection.']

by yangjianxiang

Hi： We upgrade lava 2018 to 2021, we met the problem when we submit jobs： Job error: Invalid job data: ['Device not configured to support serial connection.', 'Device not configured to support serial connection.']

4 years, 1 month

ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)

by deffo＠gmx.de

4 years, 1 month

Lava tests

by Denis HUMEAU

Hello lava users, I have to deal with a board with a very limited storage size. Overall capacity is 64 MB, with about 30 MB remaining. This is a clear limitation for Lava usage. Hence my questions: * Is there a possibility to configure Lava tests installation on an external storage, such as an USB drive? * In Lava recent versions, is it possible to optimize the overlay tests structure? * Today, assuming that tests are stored in a git repo, for each test the complete repo is copied in each overlay * A balance has to be made between one git containing all the tests and one git per test (extreme configurations) * Is there a better way to manage this? In a ideal world, that would mean copy only what is needed and not more Thanks, have a nice day

4 years, 1 month

Re: [Lava-users] lava-worker service throws error for 2021.01

by koti

Hi, I have debugged this issue a bit. Somehow I am able to register (may be work around) my lava-worker succesfully in master by update the sting as "return True" from "Return False" at " https://github.com/Linaro/lava/blob/master/lava_scheduler_app/utils.py#L339" But, I have not understand why my Lava Master "ip address"/"server name" fails while check under "def is_ip_allowed()" i.e " https://github.com/Linaro/lava/blob/master/lava_scheduler_app/utils.py#L333" appreciate any suggestions. Regards, Koti On Wed, 17 Feb 2021 at 17:30, <lava-users-request(a)lists.lavasoftware.org> wrote: > Send Lava-users mailing list submissions to > lava-users(a)lists.lavasoftware.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.lavasoftware.org/mailman/listinfo/lava-users > or, via email, send a message with subject or body 'help' to > lava-users-request(a)lists.lavasoftware.org > > You can reach the person managing the list at > lava-users-owner(a)lists.lavasoftware.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Lava-users digest..." > > > Today's Topics: > > 1. lava-worker service throws error for 2021.01 (koti) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 16 Feb 2021 20:20:38 +0530 > From: koti <kotisoftwaretest(a)gmail.com> > To: lava-users(a)lists.lavasoftware.org > Subject: [Lava-users] lava-worker service throws error for 2021.01 > Message-ID: > < > CAFW5HqSh8WMKaa6D-1p4DG3DRAM0agOP8UiAs0z-31Jxbfkn+A(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi, > > We have installed the lava-worker (2021.01) as per > > https://staging.validation.linaro.org/static/docs/v2/pipeline-server.html#i… > > but noticed the below errors on "lava-worker" and "lava-master" servers as > below. > > Lava-worker server error: (Attached the "/etc/lava-dispatcher/lava-worker" > worker configuration file) > ##################### > pi@lavaworker-1:~ $ tail -f /var/log/lava-dispatcher/lava-worker.log > 2021-02-16 19:43:08,484 ERROR [INIT] -> server error: code 403 > 2021-02-16 19:43:13,502 ERROR [INIT] -> server error: code 403 > 2021-02-16 19:43:14,896 INFO [INIT] LAVA worker has started. > 2021-02-16 19:43:14,896 INFO [INIT] Name : 'lavaworker-1' > 2021-02-16 19:43:14,896 INFO [INIT] Server : 'http://lavamasterserver' > 2021-02-16 19:43:14,897 INFO [INIT] Version: '2021.01' > 2021-02-16 19:43:14,897 INFO [INIT] Token : '<auto register>' > 2021-02-16 19:43:14,897 DEBUG [INIT] Auto register as 'raspberrypi' > 2021-02-16 19:43:14,909 ERROR [INIT] -> server error: code 403 > 2021-02-16 19:43:14,909 DEBUG [INIT] --> {"error": "Auto registration is > forbidden for '192.168.1.5'"} > 2021-02-16 19:43:19,914 DEBUG [INIT] Auto register as 'raspberrypi' > 2021-02-16 19:43:19,927 ERROR [INIT] -> server error: code 403 > 2021-02-16 19:43:19,927 DEBUG [INIT] --> {"error": "Auto registration is > forbidden for '192.168.1.5'"} > > > Lava-server server error: > #################### > lavamasterserver@lavamasterserver:/var/log$ sudo tail -f > /var/log/apache2/lava-server.log > 10.138.202.62 - - [16/Feb/2021:20:09:06 +0530] "POST > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" > 10.138.202.62 - - [16/Feb/2021:20:09:11 +0530] "POST > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" > 10.138.202.62 - - [16/Feb/2021:20:09:16 +0530] "POST > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" > 10.138.202.62 - - [16/Feb/2021:20:09:21 +0530] "POST > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" > 10.138.202.62 - - [16/Feb/2021:20:09:26 +0530] "POST > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" > 10.138.202.62 - - [16/Feb/2021:20:09:31 +0530] "POST > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" > 10.138.202.62 - - [16/Feb/2021:20:09:36 +0530] "POST > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" > 10.138.202.62 - - [16/Feb/2021:20:09:41 +0530] "POST > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" > 10.138.202.62 - - [16/Feb/2021:20:09:46 +0530] "POST > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" > 10.138.202.62 - - [16/Feb/2021:20:09:51 +0530] "POST > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" > 10.138.202.62 - - [16/Feb/2021:20:09:56 +0530] "POST > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" > > > > I feel that it may be an issue in lava master apache configuration . > appreciate any suggestions. > > > Regards, > Koti >

4 years, 2 months

Re: [Lava-users] lava-worker service throws error for 2021.01

by koti

Thanks Stevan. It is working by updating the UI token as per your suggetion. (netmask not yet worked . may be we need to cross check our steps for netmask method) Appreciated your support. Regards, Koti On Wed, 17 Feb 2021 at 19:13, <lava-users-request(a)lists.lavasoftware.org> wrote: > Send Lava-users mailing list submissions to > lava-users(a)lists.lavasoftware.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.lavasoftware.org/mailman/listinfo/lava-users > or, via email, send a message with subject or body 'help' to > lava-users-request(a)lists.lavasoftware.org > > You can reach the person managing the list at > lava-users-owner(a)lists.lavasoftware.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Lava-users digest..." > > > Today's Topics: > > 2. Re: lava-worker service throws error for 2021.01 > (Stevan Radakovi?) > > > ---------------------------------------------------------------------- > > > Message: 2 > Date: Wed, 17 Feb 2021 14:43:18 +0100 > From: Stevan Radakovi? <stevan.radakovic(a)linaro.org> > To: lava-users(a)lists.lavasoftware.org > Subject: Re: [Lava-users] lava-worker service throws error for 2021.01 > Message-ID: <ab57fe22-2a1c-a6d1-f0b4-ec97763a681e(a)linaro.org> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hello, > > Please check out this page in the docs: > > https://lava.readthedocs.io/en/latest/admin/advanced-tutorials/deploying-rp… > You need to setup either a token for each individual worker or add the > autoregistration netmask. > > Thanks, > > > On 2/16/21 3:50 PM, koti wrote: > > Hi, > > > > We have installed the lava-worker (2021.01) as per > > > https://staging.validation.linaro.org/static/docs/v2/pipeline-server.html#i… > > < > https://staging.validation.linaro.org/static/docs/v2/pipeline-server.html#i… > > > > > > but noticed the below errors on "lava-worker" and "lava-master" > > servers as below. > > > > Lava-worker server error: (Attached the > > "/etc/lava-dispatcher/lava-worker"? worker configuration file) > > ##################### > > pi@lavaworker-1:~ $ tail -f /var/log/lava-dispatcher/lava-worker.log > > 2021-02-16 19:43:08,484 ? ERROR [INIT] -> server error: code 403 > > 2021-02-16 19:43:13,502 ? ERROR [INIT] -> server error: code 403 > > 2021-02-16 19:43:14,896 ? ?INFO [INIT] LAVA worker has started. > > 2021-02-16 19:43:14,896 ? ?INFO [INIT] Name ? : 'lavaworker-1' > > 2021-02-16 19:43:14,896 ? ?INFO [INIT] Server : > > 'http://lavamasterserver <http://lavamasterserver>' > > 2021-02-16 19:43:14,897 ? ?INFO [INIT] Version: '2021.01' > > 2021-02-16 19:43:14,897 ? ?INFO [INIT] Token ?: '<auto register>' > > 2021-02-16 19:43:14,897 ? DEBUG [INIT] Auto register as 'raspberrypi' > > 2021-02-16 19:43:14,909 ? ERROR [INIT] -> server error: code 403 > > 2021-02-16 19:43:14,909 ? DEBUG [INIT] --> {"error": "Auto > > registration is forbidden for '192.168.1.5'"} > > 2021-02-16 19:43:19,914 ? DEBUG [INIT] Auto register as 'raspberrypi' > > 2021-02-16 19:43:19,927 ? ERROR [INIT] -> server error: code 403 > > 2021-02-16 19:43:19,927 ? DEBUG [INIT] --> {"error": "Auto > > registration is forbidden for '192.168.1.5'"} > > > > > > Lava-server server error: > > #################### > > lavamasterserver@lavamasterserver:/var/log$ sudo tail -f > > /var/log/apache2/lava-server.log > > 10.138.202.62 - - [16/Feb/2021:20:09:06 +0530] "POST > > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker > > 2021.01" > > 10.138.202.62 - - [16/Feb/2021:20:09:11 +0530] "POST > > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker > > 2021.01" > > 10.138.202.62 - - [16/Feb/2021:20:09:16 +0530] "POST > > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker > > 2021.01" > > 10.138.202.62 - - [16/Feb/2021:20:09:21 +0530] "POST > > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker > > 2021.01" > > 10.138.202.62 - - [16/Feb/2021:20:09:26 +0530] "POST > > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker > > 2021.01" > > 10.138.202.62 - - [16/Feb/2021:20:09:31 +0530] "POST > > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker > > 2021.01" > > 10.138.202.62 - - [16/Feb/2021:20:09:36 +0530] "POST > > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker > > 2021.01" > > 10.138.202.62 - - [16/Feb/2021:20:09:41 +0530] "POST > > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker > > 2021.01" > > 10.138.202.62 - - [16/Feb/2021:20:09:46 +0530] "POST > > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker > > 2021.01" > > 10.138.202.62 - - [16/Feb/2021:20:09:51 +0530] "POST > > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker > > 2021.01" > > 10.138.202.62 - - [16/Feb/2021:20:09:56 +0530] "POST > > /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker > > 2021.01" > > > > > > > > I feel that it may be an issue in lava master apache configuration . > > appreciate any suggestions. > > > > > > Regards, > > Koti > > > > _______________________________________________ > > Lava-users mailing list > > Lava-users(a)lists.lavasoftware.org > > https://lists.lavasoftware.org/mailman/listinfo/lava-users > > -- > Stevan Radakovi? | LAVA Senior Engineer > Linaro.org <www.linaro.org> ? Open source software for ARM SoCs > >

4 years, 2 months

lava-worker service throws error for 2021.01

by koti

Hi, We have installed the lava-worker (2021.01) as per https://staging.validation.linaro.org/static/docs/v2/pipeline-server.html#i… but noticed the below errors on "lava-worker" and "lava-master" servers as below. Lava-worker server error: (Attached the "/etc/lava-dispatcher/lava-worker" worker configuration file) ##################### pi@lavaworker-1:~ $ tail -f /var/log/lava-dispatcher/lava-worker.log 2021-02-16 19:43:08,484 ERROR [INIT] -> server error: code 403 2021-02-16 19:43:13,502 ERROR [INIT] -> server error: code 403 2021-02-16 19:43:14,896 INFO [INIT] LAVA worker has started. 2021-02-16 19:43:14,896 INFO [INIT] Name : 'lavaworker-1' 2021-02-16 19:43:14,896 INFO [INIT] Server : 'http://lavamasterserver' 2021-02-16 19:43:14,897 INFO [INIT] Version: '2021.01' 2021-02-16 19:43:14,897 INFO [INIT] Token : '<auto register>' 2021-02-16 19:43:14,897 DEBUG [INIT] Auto register as 'raspberrypi' 2021-02-16 19:43:14,909 ERROR [INIT] -> server error: code 403 2021-02-16 19:43:14,909 DEBUG [INIT] --> {"error": "Auto registration is forbidden for '192.168.1.5'"} 2021-02-16 19:43:19,914 DEBUG [INIT] Auto register as 'raspberrypi' 2021-02-16 19:43:19,927 ERROR [INIT] -> server error: code 403 2021-02-16 19:43:19,927 DEBUG [INIT] --> {"error": "Auto registration is forbidden for '192.168.1.5'"} Lava-server server error: #################### lavamasterserver@lavamasterserver:/var/log$ sudo tail -f /var/log/apache2/lava-server.log 10.138.202.62 - - [16/Feb/2021:20:09:06 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:11 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:16 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:21 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:26 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:31 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:36 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:41 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:46 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:51 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:56 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" I feel that it may be an issue in lava master apache configuration . appreciate any suggestions. Regards, Koti

4 years, 2 months

Configuring Site and domain for docker-compose setup

by Westermann, Oliver

Hey, I'm hosting a lava-setup for us which is based upon the lava-docker-compose setup from here https://git.lavasoftware.org/lava/pkg/docker-compose I managed to configure Django to use a EMAIL_HOST which allows me to notify my users. However dbutils.get_domain() returns example.com and some digging lead me to the site setup from Django. I'm not entirely sure how it's intended to work but I would expect that LAVA fetches the host to use from .env, where I specified DC_LAVA_SERVER_HOSTNAME=lava.mydomain.com. Where would I set that or what did I miss? Also: I figured out a few details about the docker-compose setup by now, eg how to configure LDAP. Where would I add such documentation? A PR to the docs? Best regards, Olli

4 years, 2 months

Problem with https and WS_URL

by Philippe Mazet (OSS)

Hello, While testing 2020.10 with https enabled, we have noticed the following problem: In /etc/lava-dispatcher/lava-worker, if we set WS_URL="--ws-url http://<master's address>/ws/" (or do not this variable at all), we get the following error on worker: 2020-11-19 15:14:57,751 INFO PING => server SSL error in data received protocol: <asyncio.sslproto.SSLProtocol object at 0x7f9a0d704160> transport: <_SelectorSocketTransport fd=8 read=polling write=<idle, bufsize=0>> Traceback (most recent call last): File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received ssldata, appdata = self._sslpipe.feed_ssldata(data) File "/usr/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata self._sslobj.unwrap() File "/usr/lib/python3.7/ssl.py", line 767, in unwrap return self._sslobj.shutdown() ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609) Still, even with those errors the worker is fully functional. Now, the only way to get rid of such errors is to explicitly specify the port, 8001: WS_URL="--ws-url http://<master's address>:8001/ws/" Have you experienced similar problems? Did we miss something on our setup? Thanks a lot, Philippe

4 years, 2 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users February 2021