- lava-users - op-lists.linaro.org

Integration of a new device: QC-DB-P10003

by Marcel Trattner

Dear LAVA-Users, We are trying to integrate a new device into our LAVA infrastructure, apart from our work with Raspberry Pis. We still lack experience with LAVA and I wanted to reach out to the community for some help with the setup. The Device we want to integrate is a QC-DB-P10003 from mouser with Android 9 and the following specifications: [cid:image001.png@01D71691.AA0089F0] Also here<https://www.mouser.de/ProductDetail/515-QC-DB-P10003/> a link to the product page, which contains the complete data sheet for the device. Does someone have experience with this device and can give some advice on how to create a device templates or if there is already one available in LAVA which would work. Also tips for defining a device dictionary and test jobs to run Android on this device are very welcome. Has anyone maybe configured a similar device and can suggest us some Steps on how to proceed. Kind Regards, Marcel _____________________________________________________________________________________ Expleo Germany GmbH Sitz der Gesellschaft | Corporate Headquarters: M?nchen Handelsregister | Commercial Register: Amtsgericht M?nchen HRB 83252 Gesch?ftsf?hrung | Management: Ralph Gillessen, Marcus Ganguin This message contains information that may be privileged or confidential. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. _________________________________________________________ EMAIL LEGAL MENTION / DISCLAIMER This message contains information that may be privileged or confidential and is the property of the Expleo Services SAS, RCS Versailles 831 178 348, located, 3 avenue des Pr?s, 78180 Montigny Le Bretonneux - France. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. Ce message contient des informations qui peuvent ?tre privil?gi?es ou confidentielles et elles sont de la propri?t? d'Expleo Services SAS, RCS Versailles 831 178 348, situ?, 3 avenue des Pr?s, 78180 Montigny le Bretonneux-France. Il est destin? uniquement ? la personne ? qui est adress?. Si vous n'?tes pas le destinataire vis?, vous n'?tes pas autoris? ? lire, imprimer, conserver, copier, diffuser, distribuer ou utiliser ce message ou toute partie de celui-ci. Si vous recevez ce message par erreur, veuillez en avertir imm?diatement l'exp?diteur et supprimer toutes les copies de ce message.

5 years

2
1
0 0

About deploy overlay.

by Larry Shen

Hi, It looks only the scripts in "lava_dispatcher\lava_test_shell" will be overlayed to rootfs when lava do deploy. So, my question is: If we have some way in job to define a script file location: e.g. http://site/a.sh, then lava could also fetch the http://site/a.sh, then overlay it to rootfs? Does lava has such kinds of manipulate rootfs function already? Or I have to put this scripts in the /usr/lib/python3/dist-packages/lava_dispatch/lava_test_shell of every worker? Thanks.

5 years

2
1
0 0

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"?

5 years

2
1
0 0

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.']

5 years

2
1
0 0

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

by deffo＠gmx.de

5 years

2
1
0 0

Job not exiting after completion

by DAS, BHARGAV

Hi Lava Users, After upgrading to LAVA 2021.01, we are facing an issue of jobs not completing/exiting (once submitted) and getting stuck in "Running" state, doesn't matter if the job is successful or unsuccessful/incomplete/fail. After sometime if we try to cancel the job it gets stuck in "Cancelling" state. Due to this the device gets blocked and subsequent jobs are sent to "Scheduled" state. Now only possible solution to free up the device, is to delete the job from LAVA administration LAVA Administration > Test jobs (under lava_scheduler_app) > {job id} > Delete . Though this way the device is recovered but the whole job gets deleted. I have tried with different boot and deploy methods like nfs, uuu, ums, and minimal. In all cases I am getting similar issue. This issue is only observed while using imx devices. Ssh based jobs are working properly and also other x86 based devices while booting through minimal method. I have attached screenshot of the jobs (Lava-job-begin.PNG and Lava-job-end.PNG). What can be the issue here ? Thanks, Bhargav

5 years

2
1
0 0

Re: [Lava-users] LAVA master backup/restore

by Philippe Mazet (OSS)

Thanks a lot for your reply! The LAVA link you sent seems pretty outdated, and I don't think it can be applied as-is to docker-compose solution. It is for a host install on Debian (not Docker). More recent documentation seems to be here: https://lava.readthedocs.io/en/latest/admin/basic-tutorials/instance/backup/ However it tells how to create a .sql backup file (which I have), not how to restore it. About the postgres link you sent, it is for postgres running on host, not within docker I think. For Docker, it is described in https://registry.hub.docker.com/_/postgres/ (chapter "Initialization scripts"). But then when I try to place my .sql file in /docker-entrypoint-initdb.d/ folder, I get the error mentioned in my email: database "lavaserver" already exists. Thus my question: what procedure is followed by Linaro for the backup/restore of their docker-compose instances? Thanks again, Philippe From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of koti Sent: Friday, March 19, 2021 2:15 PM To: lava-users(a)lists.lavasoftware.org Subject: [Lava-users] LAVA master backup/restore Hi Philippe Mazet, Please find my comments inline. Questions: - Does Linaro's docker-compose solution modify postgres restore mechanism in any way? [Koti] --> I am not sure about this. - How do you handle backup/restore at linaro? [Koti] ----> still are you facing the backup/restore issue after following the below documentation? 1. https://docs.lavasoftware.org/lava/admin-backups.html 2. http://postgresguide.com/utilities/backup-restore.html Regards, Koti On Fri, 19 Mar 2021 at 17:30, <mailto:lava-users-request@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 master backup/restore (Philippe Mazet (OSS)) ---------------------------------------------------------------------- Message: 1 Date: Thu, 18 Mar 2021 15:22:20 +0000 From: "Philippe Mazet (OSS)" <mailto:philippe.mazet@oss.nxp.com> To: "mailto:lava-users@lists.lavasoftware.org" <mailto:lava-users@lavasoftware.org> Subject: [Lava-users] LAVA master backup/restore Message-ID: <PR3PR04MB7244B9C1456CAD918574F1218B699(a)PR3PR04MB7244.eurprd04.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" Hi all, I am using the docker-compose solution to run a master: https://git.lavasoftware.org/lava/pkg/docker-compose I was wondering how to extract a backup of the DB, and re-inject it in a different instance. I found that postgres image has its own "restore" mechanism, based on initdb.d folder, as mentioned in the documentation: https://registry.hub.docker.com/_/postgres/ The entrypoint.sh script (https://github.com/docker-library/postgres/blob/master/docker-entrypoint.sh) handles the restore whenever the folder is /docker-entrypoint-initdb.d/ contains a .sql file. But when we store a backup in the container's /docker-entrypoint-initdb.d/ folder, and remove both the postgres image and its db-data volume, we get this error on next start: ERROR: database "lavaserver" already exists Full startup log attached. Questions: - Does Linaro's docker-compose solution modify postgres restore mechanism in any way? - How do you handle backup/restore at linaro? Thanks a lot in advance, Philippe Mazet NXP Semiconductors - Edge Processing Email: philippe.mazet(a)nxp.com

5 years

1
0
0 0

LAVA master backup/restore

by koti

Hi Philippe Mazet, Please find my comments inline. Questions: - Does Linaro's docker-compose solution modify postgres restore mechanism in any way? [Koti] --> I am not sure about this. - How do you handle backup/restore at linaro? [Koti] ----> still are you facing the backup/restore issue after following the below documentation? 1. https://docs.lavasoftware.org/lava/admin-backups.html 2. http://postgresguide.com/utilities/backup-restore.html Regards, Koti On Fri, 19 Mar 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 master backup/restore (Philippe Mazet (OSS)) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 18 Mar 2021 15:22:20 +0000 > From: "Philippe Mazet (OSS)" <philippe.mazet(a)oss.nxp.com> > To: "lava-users(a)lists.lavasoftware.org" <lava-users(a)lavasoftware.org> > Subject: [Lava-users] LAVA master backup/restore > Message-ID: > < > PR3PR04MB7244B9C1456CAD918574F1218B699(a)PR3PR04MB7244.eurprd04.prod.outlook.com > > > > Content-Type: text/plain; charset="us-ascii" > > Hi all, > > I am using the docker-compose solution to run a master: > https://git.lavasoftware.org/lava/pkg/docker-compose > I was wondering how to extract a backup of the DB, and re-inject it in a > different instance. > > I found that postgres image has its own "restore" mechanism, based on > initdb.d folder, as mentioned in the documentation: > https://registry.hub.docker.com/_/postgres/ > > The entrypoint.sh script ( > https://github.com/docker-library/postgres/blob/master/docker-entrypoint.sh) > handles the restore whenever the folder is /docker-entrypoint-initdb.d/ > contains a .sql file. > > But when we store a backup in the container's > /docker-entrypoint-initdb.d/ folder, and remove both the postgres image and > its db-data volume, we get this error on next start: > ERROR: database "lavaserver" already exists > Full startup log attached. > > Questions: > - Does Linaro's docker-compose solution modify postgres restore mechanism > in any way? > - How do you handle backup/restore at linaro? > > Thanks a lot in advance, > > > Philippe Mazet > NXP Semiconductors - Edge Processing > Email: philippe.mazet(a)nxp.com > > > >

5 years

1
0
0 0

Why the latest version of lava is 2019.11?

by cnspring2002

Hello, lava owners: I follow https://validation.linaro.org/static/docs/v2/installing_on_debian.html to install. But after add next, and apt update I found the latest lava is 2019.11 deb https://apt.lavasoftware.org/release buster main root@9486058b8151:~# apt-cache policy lava-server lava-server: Installed: (none) Candidate: 2019.11+buster Version table: 2019.11+buster 500 500 https://apt.lavasoftware.org/release buster/main amd64 Packages 2019.01-5 500 500 http://deb.debian.org/debian buster/main amd64 Packages What happened here? Or I made something wrong?

5 years

2
1
0 0

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

5 years, 1 month

3
2
0 0

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 >

5 years, 1 month

1
3
0 0

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 > >

5 years, 1 month

1
0
0 0

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

5 years, 1 month

2
1
0 0

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

5 years, 1 month

2
2
0 0

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

5 years, 1 month

3
4
0 0

Sometime we met the problem blow occasionally，but it succeed when we resubmit the job

by yangjianxiang

Hey： Sometime we met the problem blow occasionally，but it succeed when we resubmit the job How can we solve the problem？ [cid:image001.png@01D6FE33.5DDDEA20]

5 years, 1 month

2
1
0 0

Lava-->Results page gives the error "500 Internal Server Error"

by koti koti

Hi Recently my LAVA results page through the below error (Attached the screenshot). Is there any way to fix this? " 500 Internal Server Error Reverse for 'lava.results.suite' with arguments '(77, '0_bin utility tests')' not found. 1 pattern(s) tried: ['results/(?P<job>[0-9]+|[0-9]+\\.[0-9]+)/(?P<pk>[-_a-zA-Z0-9.]+)$'] " Regards, Koti

5 years, 2 months

3
4
0 0

When we install lava 2021.01 in debian 10.6, we met the problem like this

by yangjianxiang

Hi： When we install lava 2021.01 in debian 10.6, we met the problem like this： [cid:image001.png@01D6F9A1.EF5DC880]

5 years, 2 months

2
1
0 0

How lava schedule jobs to devices？ Where is the code and how it works

by yangjianxiang

Hello： we want to learn more about lava, but we do not know lava very well, can you give us some tips about: 1、How lava schedule jobs to devices？ Where is the code and how it works. thanks

5 years, 2 months

2
1
0 0

Unable to change device health state without being admin

by Sebastien Haezebrouck

Hi, We used to set devices access permission using groups. So we would restrict access to a subset of devices to members of a specific group. When switching to lava 2020.10, it seems the permission to change a device does not allow to change device health state anymore. This used to be possible in previous version, and was very convenient for maintenance. With 2020.10 it seems only a lava admin is allowed to change a device health. Is it the expected behavior ? Did I miss an option somewhere ? A bit more details: All our devices are set to: * “device owner”->”Group with physical access” -> our_group. * “group device permissions”->”lava_sched_app |device | Can change device” -> “Group” -> our_group. * I intentionally did not give any specific permission to the “our_group” group, like “Can change device”, since it would allow members of this group to change any devices. Access control has to work both ways 😊 Kind regards, Seb

5 years, 2 months

3
3
0 0

Issue with DUT reboot command with uuu boot method (ssh login)

by Anand, Ravi

Hello All, I am currently facing one issue where I have to execute reboot (soft reboot) command in DUT. But after executing reboot command , target is getting rebooted and lava job get stuck at login prompt. To overcome this I have inserted boot section with auto_login (waiting for login prompt to pass username & password). But with this scenario, just after reboot command , target is getting rebooted (Hard reset) by PDU. Can somebody help me on this. I don't want DUT to get hard reset by PDU. Expectation is like just after reboot command, wait for login prompt and then proceed it with another set of commands. Attached both scenario sample pipeline definitions for reference. Regards, Ravi Anand

5 years, 2 months

2
2
0 0

Re: [Lava-users] Subject: Issue with DUT reboot command with uuu boot

by koti koti

Hi Ravi Anand, Can you try using "Method: minimal" ? Reference: https://docs.lavasoftware.org/lava/actions-boot.html#minimal) Example: ####### " actions: - boot: timeout: minutes: 2 method: minimal " Note: 1. You can mention your custom soft reboot command using the string "soft_reboot" or "{% set soft_reboot_command = 'reset' %}" in corresponding files. Regards, Koti On Fri, 8 Jan 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. Issue with DUT reboot command with uuu boot method (ssh > login) (Anand, Ravi) > 2. Ask android vts test link in docker test shell. (Larry Shen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 7 Jan 2021 18:12:55 +0000 > From: "Anand, Ravi" <Ravi_Anand(a)mentor.com> > To: "lava-users(a)lists.lavasoftware.org" > <lava-users(a)lists.lavasoftware.org> > Subject: [Lava-users] Issue with DUT reboot command with uuu boot > method (ssh login) > Message-ID: > <b010fbd1eff04d168a44bc3ecb661a69(a)svr-orw-mbx-03.mgc.mentorg.com> > Content-Type: text/plain; charset="us-ascii" > > Hello All, > > I am currently facing one issue where I have to execute reboot (soft > reboot) command in DUT. But after executing reboot command , target is > getting rebooted and lava job get stuck at login prompt. > To overcome this I have inserted boot section with auto_login (waiting for > login prompt to pass username & password). But with this scenario, just > after reboot command , target is getting rebooted (Hard reset) by PDU. > > Can somebody help me on this. I don't want DUT to get hard reset by PDU. > Expectation is like just after reboot command, wait for login prompt and > then proceed it with another set of commands. > > Attached both scenario sample pipeline definitions for reference. > > Regards, > Ravi Anand >

5 years, 2 months

2
1
0 0

TR: issue with lava agent installation

by MARVIN Trijasse

Hello, As a new member of DI team from Schneider electric I have an issue when installing my lava agent on our raspberry pi. I followed this procedure https://collaborate.linaro.org/pages/viewpage.action?pageId=118293253#Getti… as I run the docker_compose build I get this error ERROR: Service 'lava-dispatcher' failed to build : no matching manifest for linux/arm/v7 in the manifest list entries (see image in attachment) Marvin Trijasse

5 years, 2 months

2
1
0 0

Worker/master version mismatch

by Philippe Mazet (OSS)

Hi All, Since 2020.09 it appears that workers using a version different than the master are refusing to start. Would it be possible to relax this constraint? With workers spread all over the world in different places, it is hard to synchronize master and slaves upgrades. Also, we have always run with workers versions <= master version, without a single problem. So it would be great to allow version mismatch, and maybe print a simple warning when version differs? Thanks, Philippe

5 years, 2 months

2
3
0 0

Regarding lava installation facing problem

by Satishkumar Rajguru

Hi All, this is the first time I am communicating with the lava community. I am facing a problem with the lava installation. I need step by step installation procedure and after installation one example demo for the understanding purpose. (send all steps because I am first time using the lava ) in that, I am facing a problem when I type the command $sudo apt-get install lava-server then getting the following error message : --------------------------------------------------------------------------------------------------------------------------------------------------------- File "/usr/lib/python3/dist-packages/lava_rest_app/v02/routers.py", line 22 from import views ^ SyntaxError: invalid syntax migration dpkg: error processing package lava-server (--configure): installed lava-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: lava-server E: Sub-process /usr/bin/dpkg returned an error code (1) ------------------------------------------------------------------------------------------------------------------------------------------------------------- please send the information from the first command of installation to the last command of installation which I need to use. Note: I am using Ubuntu 18.04.5 LTS. Thank You.

5 years, 2 months

2
1
0 0

Failed to start lava-master.service: Unit lava-master.service not found.

by Singamsetty Nagendra

Hi, I am trying to upgrade the lava server and remote workers in my lab from 2020.08 to 2020.10(latest). *I have used following steps to upgrade:* $ wget https://apt.lavasoftware.org/lavasoftware.key.asc $ sudo apt-key add lavasoftware.key.asc OK sudo apt update sudo apt upgrade lava I am getting the following Error while restarting the lava-master : *root@LavaServer:/# service lava-master start Failed to start lava-master.service: Unit lava-master.service not found.* Even the remote worker side also got the same error message: *lava@alif-blr-worker02/# service lava-slave start Failed to start lava-slave.service: Unit lava-slave.service not found.* Able to start/stop lava-server-gunicorn root@LavaServer:/# service lava-server-gunicorn start On Master(lava server): following services are enabled after upgrade(2020.10) *root@LavaServer:/# systemctl list-unit-files | grep enabled |grep lavalava-coordinator.service enabled lava-publisher.service enabled lava-scheduler.service enabled lava-server-gunicorn.service enabled lava-worker.service enabled root@LavaServer:/# root@LavaServer:/#* On Worker following services are enabled after upgrade:(2020.10) *lava@alif-blr-worker02:~$ systemctl list-unit-files | grep enabled |grep lavalava-worker.service enabled * Another Worker which is not upgraded to 2020.10 :(It is running with 2020.08) *Following services are Enabled * *root@alif-blr-worker03:/# systemctl list-unit-files | grep enabled |grep lavalava-coordinator.service enabled lava-logs.service enabled lava-master.service enabled lava-publisher.service enabled lava-server-gunicorn.service enabled lava-slave.service enabled root@alif-blr-worker03:/# * *I am getting this issue with 2020.10 . I haven't seen this issue with previous version upgrades. * Kindly help me out to solve this issue!! Thanks!! Regards Nagendra S

5 years, 2 months

2
1
0 0

Some question about lava V2 2018.11+stretch，waiting for your answer，thanks very much

by yangjianxiang

Hi lava： Some question about lava V2 2018.11+stretch： 1、 As lava running for weeks，it tasks minutes for the master to schedule jobs to the lava-slave ，and the normal time maybe 20s below. When we restar both lava master and lava slave，it schedule job in 20s again. Can you tell us how to solve the problem，thanks very mutch. [cid:image002.png@01D6F0D5.449B7F70] 2、we want to know how lava code works，can you give us some document. Sometimes we want to modify the lava steps，but we don’t know how to do.

5 years, 2 months

3
2
0 0

WG: Help with new device integration

by Marcel Trattner

Dear Lava-Team, I contacted you a few weeks ago for some help with the integration of a new device. We got a bit further thanks to you but we're faceing some new issues and we hoped that you could help us with this. We are using the official Docker-Compose<https://git.lavasoftware.org/lava/pkg/docker-compose> repository and specified a new device dictionary on the server container. As a device type we use a newly created device type that extends base-fastboot device-type, which looks like this: {% extends 'rse22.jinja2' %} {% set power_on_command = 'python ./root/power-control/ppson.py' %} {% set power_off_command = 'python ./root/power-control/ppsoff.py' %} {% soft_reboot_command = 'reboot' %} {% hard_reset_command = 'python ./root/power-control/ppsoff.py && sleep 5 && python ./root/power-control/ppson.py' %} {% set connection_list = [uart0] %} {% set connection_commands = {uart0: telnet <ip_host_machine> 7101} %} {% set connection_tags = {uart0: [primary, 'telnet']} %} But with this we received the following error: [cid:image001.png@01D6EE7C.31C35A90] The error disappeared however when we removed the following lines: {% set power_on_command = 'python ./root/power-control/ppson.py' %} {% set power_off_command = 'python ./root/power-control/ppsoff.py' %} {% soft_reboot_command = 'reboot' %} {% hard_reset_command = 'python ./root/power-control/ppsoff.py && sleep 5 && python ./root/power-control/ppson.py' %} With those lines we are trying to trigger the scripts, which control our power supply directly. Do we have to pay attention to the python dependencies in the scripts or could the error be in the definition itself? We thought, that we had at least configured the device dictionary sufficiently to have a connection to the device and start a very basic health check. Our device runs Linux, which is running Android on top. The Ser2Net connection has been configured according to the instructions on the repo as well (using the telnet command by itself worked fine). So we specified the health check like this: device_type: rsu job_name: Health Check for RSU timeouts: job: minutes: 30 action: minutes: 5 connection: minutes: 2 priority: medium visibility: public actions: - deploy: namespace: tlxc timeout: minutes: 5 to: lxc packages: - android-tools-adb - android-tools-fastboot - boot: method: lxc prompts: - 'root@(.*):/#' timeout: minutes: 5 - test: timeout: minutes: 4 definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: hello-world description: "say hello" os: - android scope: - functional run: steps: - apt -q update - pwd - echo "echo hello" # remember to use -y to allow apt to proceed without interaction # -q simplifies the apt output for logging. from: inline name: hello-world path: inline/hello-world.yaml When executing, we got the following error: [cid:image002.png@01D6EE7E.9CED3690] Could you please give us some advice, on how to define a test job/health check for a device, which uses fast-boot and Android? Your help would be greatly appreciated. Best regards, Marcel _________________________________________________________ EMAIL LEGAL MENTION / DISCLAIMER This message contains information that may be privileged or confidential and is the property of the Expleo Services SAS, RCS Versailles 831 178 348, located, 3 avenue des Pr?s, 78180 Montigny Le Bretonneux - France. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. Ce message contient des informations qui peuvent ?tre privil?gi?es ou confidentielles et elles sont de la propri?t? d'Expleo Services SAS, RCS Versailles 831 178 348, situ?, 3 avenue des Pr?s, 78180 Montigny le Bretonneux-France. Il est destin? uniquement ? la personne ? qui est adress?. Si vous n'?tes pas le destinataire vis?, vous n'?tes pas autoris? ? lire, imprimer, conserver, copier, diffuser, distribuer ou utiliser ce message ou toute partie de celui-ci. Si vous recevez ce message par erreur, veuillez en avertir imm?diatement l'exp?diteur et supprimer toutes les copies de ce message.

5 years, 2 months

2
1
0 0

Define "Missing key" Whitelist

by Westermann, Oliver

Hey, we recently updated our LAVA setup from 2020.06 to 2020.12. After a few hickups we’re back running, but we are greeted with a few new warnings: Our setup uses the iMX8 and the UUU boot method, which uses several, internal variables. Internal = Internal to U-Boot or bash, for example: > FB: ucmd setenv fastboot_buffer ${loadaddr} > FBK: ucmd mkfs.ext4 -F -E nodiscard /dev/mmcblk${mfg_mmcdev}p1 With the recent LAVA version, this causes a warning: {"dt": "2021-01-25T07:43:46.551216", "lvl": "warning", "msg": "Missing key : '{mfg_mmcdev}' for string 'ucmd mkfs.ext4 -F -E nodiscard /dev/mmcblk${mfg_mmcdev}p1'"} While I could reduce this by removing the brackets in the first case, this won’t work for the second case. Is there a way to provide eg a variable whitelist? The 30 warnings boil down to 4-5 variables, so this might be a useful feature addition. Any other ideas of cause welcome, maybe I will try to use this for my first contribution here 😊 Best regards, Olli

5 years, 2 months

2
1
0 0

Docker transfer_overlays problem

by Seb Seb

Hi, I am having a problem with using the transfer_overlays command for a dispatcher in docker. I cannot set the dispatcher ip no matter what I try. I have tried using the API here : " http://10.1.51.55/api/v0.2/workers/docker_dispatcher_hostname/config/" but I get this error when posting : ""detail": "CSRF Failed: CSRF token missing or incorrect.", I have tried another browser already. I have also tried creating a dispatcher.yaml file in these locations : /etc/lava-server/dispatcher.d/lava-dispatcher ; /etc/lava-server/dispatcher.d/ ; /etc/lava-server/dispatcher.d/lava-master. The ip I have set is simply ignored. Could anybody help please? Thanks

5 years, 2 months

2
1
0 0

Some question about lava V2 2018.11+stretch，waiting for your answer，thanks very much

by yangjianxiang

Hi lava： Some question about lava V2 2018.11+stretch： 1、 As lava running for weeks，it tasks minutes for the master to schedule jobs to the lava-slave ，and the normal time maybe 20s below. When we restar both lava master and lava slave，it schedule job in 20s again. Can you tell us how to solve the problem，thanks very mutch. [cid:image001.png@01D6ED8C.7BAFA000] 2、we want to know how lava code works，can you give us some document. Sometimes we want to modify the lava steps，but we don’t know how to do.

5 years, 2 months

1
0
0 0

Ask android vts test link in docker test shell.

by Larry Shen

Hi, guys, Recently we are running android VTS test in lava docker test shell, but find all MTP cases fail. It reports: 01-08 07:42:38 D/ModuleDefinition: Running module armeabi-v7a HalUsbGadgetV1_0HostTest 01-08 07:42:43 I/ModuleListener: [1/5] com.android.tests.usbgadget.HalUsbGadgetV1_0HostTest#testMtp FAILURE: java.lang.AssertionError: MTP not present at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at com.android.tests.usbgadget.HalUsbGadgetV1_0HostTest.testMtp(HalUsbGadgetV1_0HostTest.java:113) I'm a little lost currently, so before I have a deep investigation, I want to know if you can share a link about this case: com.android.tests.usbgadget.HalUsbGadgetV1_0HostTest#testMtp I know you guys run android tests on other product always, could share a link for us to reference? Or with good luck you know what's the potential root cause for my failure? Thanks.

5 years, 2 months

1
3
0 0

Unable to find settings.conf file in /etc/lava-server/ using 2020.10

by Nagendra Singamsetti

Hi team, I am Re installing my lava machines with 2020.10. But after upgrading I have noticed that settings.conf file is missing /etc/lava-server . Is this expected behaviour?? 2. I am unable to access the lava server within the intranet with the latest version 2020.10. To do this I used to modify settings.conf at /etc/lava-server/settings.conf with "ALLOWED_HOSTS" to "*". But i am getting Bad Request (400) Kindly help me out to solve this issue!! thanks Regards Nagendra S

5 years, 3 months

2
1
0 0

LAVA apt install packages

by Philippe Mazet (OSS)

Hi, It looks like the apt release is stuck to version 2019.11: https://apt.lavasoftware.org/release/dists/buster/Release Do I miss something? Then I tried to use the daily apt source to install a worker (deb https://apt.lavasoftware.org/daily buster main, mentioned on https://docs.lavasoftware.org/lava/installing_on_debian.html#debian-install…), but then I have a version mismatch with my master... Sorry to insist... but this version check is really a pain for us. A warning instead would be much more convenient. Could you please let me know how could I force install of 2020.10 for example? (I mean, a native install, not using Docker) Thank you very much, Philippe

5 years, 3 months

2
2
0 0

Re: [Lava-users] How can I upgrade my Lava software to latest version (may be 2020.10)

by koti koti

Hi Stevan, I have followed the steps mentioned in the pages provided by you i.e " https://docs.lavasoftware.org/lava/installing_on_debian.html#lava-repositor… " Still my version is same i.e "2019.01-5" You can find my complete log at https://justpaste.me/id5P . Only the thing is that I followed below steps 1. Install Debain buster 2. Run #sudo apt install lava 3. Run #sudo apt install lava-dispatcher 4. #wget https://apt.lavasoftware.org/lavasoftware.key.asc 5. #sudo apt-key add lavasoftware.key.asc 6. #sudo apt update appreciated any suggestions. Regards, Koti > > ------------------------------ > > Message: 3 > Date: Fri, 27 Nov 2020 08:57:14 +0100 > From: Stevan Radakovi? <stevan.radakovic(a)linaro.org> > To: lava-users(a)lists.lavasoftware.org > Subject: Re: [Lava-users] How can I upgrade my Lava software to latest > version (may be 2020.10) > Message-ID: <6c0c9fb0-069b-142c-59d1-2ff229f37031(a)linaro.org> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hello, > > There's everything regarding releases documented here: > > https://docs.lavasoftware.org/lava/installing_on_debian.html#lava-repositor… > < > https://docs.lavasoftware.org/lava/installing_on_debian.html#lava-repositor… > > > You will need to add LAVA signing key prior as described here: > > https://docs.lavasoftware.org/lava/installing_on_debian.html#lava-archive-s… > < > https://docs.lavasoftware.org/lava/installing_on_debian.html#lava-archive-s… > > > > Cheers, > > > On 11/27/20 8:31 AM, koti koti wrote: > > Hi, > > > > Recently I have installed Lava-Master and Lava-Dispatcher using the > > steps mentioned below in the corresponding servers. > > > > ??????????????? Server: > > ???????????????? ###### > > ?????????????????????? ?? 1. #sudo install lava > > ???????????????? Worker (Dispatcher) > > ???????????????? ################### > > ????????????????????????? 1. #sudo install lava-dispatcher > > > > But the installeve Lava software version is the old version > (*2019.01-5*). > > > > Now I want to upgrade to latest (*may be 2020.10*) lava > > (https://git.lavasoftware.org/lava/lava/-/tags > > <https://git.lavasoftware.org/lava/lava/-/tags>) > > > > Please can someone let me know the steps to upgrade my lava version to > > the latest? > > > > > > Regards, > > Koti > > > > _______________________________________________ > > Lava-users mailing list > > Lava-users(a)lists.lavasoftware.org > > https://lists.lavasoftware.org/mailman/listinfo/lava-users > > -- > Stevan Radakovi? | LAVA Engineer > Linaro.org <www.linaro.org> ? Open source software for ARM SoCs > >

5 years, 3 months

2
5
0 0

Re: [Lava-users] Unable to upgrade lava server/workers 2020.10

by koti koti

Hi, Try to list the available lava versions in your distro initially using the command "apt policy lava" and downgrade using "sudo apt install <package version>" . But, there may be cases in which you must resolve some dependencies to be able to downgrade the package through. Hope this may helps you i.e https://www.linuxuprising.com/2019/02/how-to-downgrade-packages-to-specific… *Note*: We have not tried this so far. AFAIK before executing these commands, make sure you take the backup of your lava modified/configuration files which you have changed for your production/running setup. Best of luck!!. Regards, Koti On Thu, 10 Dec 2020 at 17:30, <lava-users-request(a)lists.lavasoftware.org> wrote: > > Date: Thu, 10 Dec 2020 17:20:08 +0530 > From: Nagendra Singamsetti <nag.singam91(a)gmail.com> > To: lava-users(a)lists.lavasoftware.org > Subject: [Lava-users] Unable to upgrade lava server/workers 2020.10 > Message-ID: > < > CAFhg_WuWOCMedoDXECg+rcFdtzwPS2ei5m8Q+mpFKjhTgKqa9w(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi Team, > > 1. I am trying to upgrade lava machines with the latest version > 2020.10.previously it was running on 2020.08. > > After Upgrading with the latest 2020.10 i can see that All machines 2 > workers & 1 server went offline. Unable to start services of server/worker > due to > > *Failed to start lava-master.service: Unit lava-master.service not found.* > > *Failed to start lava-slave.service: Unit lava-slave.service not found.* > > *i have referred following page to upgrade:* > > https://lava.readthedocs.io/en/latest/admin/basic-tutorials/instance/instal… > > > 2 . I would like to know how to downgrade to previous versions. > > I am looking for your kind response !! > > Regards > Nagendra S > > ***************************************** >

5 years, 3 months

1
0
0 0

Unable to upgrade lava server/workers 2020.10

by Nagendra Singamsetti

Hi Team, 1. I am trying to upgrade lava machines with the latest version 2020.10.previously it was running on 2020.08. After Upgrading with the latest 2020.10 i can see that All machines 2 workers & 1 server went offline. Unable to start services of server/worker due to *Failed to start lava-master.service: Unit lava-master.service not found.* *Failed to start lava-slave.service: Unit lava-slave.service not found.* *i have referred following page to upgrade:* https://lava.readthedocs.io/en/latest/admin/basic-tutorials/instance/instal… 2 . I would like to know how to downgrade to previous versions. I am looking for your kind response !! Regards Nagendra S

5 years, 3 months

1
0
0 0

Re: [Lava-users] [Lava-devel] Integration of a new device

by koti koti

++ Lava-users list. Regards, Koti On Fri, 4 Dec 2020 at 17:30, <lava-devel-request(a)lists.lavasoftware.org> wrote: > Send Lava-devel mailing list submissions to > lava-devel(a)lists.lavasoftware.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.lavasoftware.org/mailman/listinfo/lava-devel > or, via email, send a message with subject or body 'help' to > lava-devel-request(a)lists.lavasoftware.org > > You can reach the person managing the list at > lava-devel-owner(a)lists.lavasoftware.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Lava-devel digest..." > > > Today's Topics: > > 1. Integration of a new device (Marcel Trattner) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 4 Dec 2020 10:50:08 +0000 > From: Marcel Trattner <marcel.trattner(a)expleogroup.com> > To: "Lava-devel(a)lists.lavasoftware.org" > <Lava-devel(a)lists.lavasoftware.org> > Cc: Alexander Wyron Wachtberger > <alexander-wyron.wachtberger(a)expleogroup.com>, Vladimir Schmidt > <vladimir.schmidt(a)expleogroup.com> > Subject: [Lava-devel] Integration of a new device > Message-ID: > < > AM9PR10MB4295B7516795BD7B514C2DF7E5F10(a)AM9PR10MB4295.EURPRD10.PROD.OUTLOOK.COM > > > > Content-Type: text/plain; charset="us-ascii" > > Dear LAVA-Team, > > We have only recently started to use LAVA in a new project and we are now > at the point of integrating a new device. As I have read in the > documentation that this is the hardest part I would like to ask for some > advice where to start and what to especially look out for. > > The current state is that LAVA, as a master and one slave is running in > two Docker containers by using the example of the following Github > repository: > > https://github.com/kernelci/lava-docker > > After reading the documentary extensively and trying things out with qemu > I'd like to try and integrate the following device: > > https://www.lantronix.com/products/sa8155p-automotive-development-platform/ > > Our plan so far would be: > Since it has a Snapdragon processor, it's running Android and it is using > fastboot for flashing, we figured we could use one of the dragonboard > Device-Type templates and duplicate it for our device. But as it comes now > to configuring the device dictionary and specifying the test jobs we are > not so sure as how to proceed and we also don't want to damage the > hardware, so we would be grateful for some help. > > Here some more information: > The DUT is connected via USB and its power supply can be turned on and off > by using Python scripts (When defining the power_on and power_off commands, > should the scripts then be on the master or on the dispatcher? And what are > all the necessary parameters for the power on/off and also the values > connection_list and connection_commands?). > It is running Android with the underlying Linux configured especially for > the hardware, so we would like to avoid deploying for the beginning and > only run some simple shell tests to see if the connection stands. > A very simple health check has been set up here< > https://paste.debian.net/1175549>, maybe you could give some feedback if > that would be sufficient and how future test jobs should be altered. > > Hope to hear from you soon > > Best Regards, > > > _________________________________________________________ > > EMAIL LEGAL MENTION / DISCLAIMER > > This message contains information that may be privileged or confidential > and is the property of the Expleo Services SAS, RCS Versailles 831 178 348, > located, 3 avenue des Pr?s, 78180 Montigny Le Bretonneux - France. It is > intended only for the person to whom it is addressed. If you are not the > intended recipient, you are not authorized to read, print, retain, copy, > disseminate, distribute, or use this message or any part thereof. If you > receive this message in error, please notify the sender immediately and > delete all copies of this message. > > Ce message contient des informations qui peuvent ?tre privil?gi?es ou > confidentielles et elles sont de la propri?t? d'Expleo Services SAS, RCS > Versailles 831 178 348, situ?, 3 avenue des Pr?s, 78180 Montigny le > Bretonneux-France. Il est destin? uniquement ? la personne ? qui est > adress?. Si vous n'?tes pas le destinataire vis?, vous n'?tes pas autoris? > ? lire, imprimer, conserver, copier, diffuser, distribuer ou utiliser ce > message ou toute partie de celui-ci. Si vous recevez ce message par erreur, > veuillez en avertir imm?diatement l'exp?diteur et supprimer toutes les > copies de ce message. >

5 years, 4 months

1
0
0 0

Failed to start lava-master.service: Unit lava-master.service not found

by Nagendra Singamsetti

Hi, I am trying to upgrade the lava server and remote workers in my lab from 2020.08 to 2020.10(latest). *I have used following steps to upgrade:* $ wget https://apt.lavasoftware.org/lavasoftware.key.asc $ sudo apt-key add lavasoftware.key.asc OK sudo apt update sudo apt upgrade lava I am getting the following Error while restarting the lava-master : *root@LavaServer:/# service lava-master startFailed to start lava-master.service: Unit lava-master.service not found.* Even the remote worker side also got the same error message: *lava@alif-blr-worker02/# service lava-slave startFailed to start lava-slave.service: Unit lava-slave.service not found.* Able to start/stop lava-server-gunicorn root@LavaServer:/# service lava-server-gunicorn start On Master(lava server): following services are enabled after upgrade(2020.10) *root@LavaServer:/# systemctl list-unit-files | grep enabled |grep lavalava-coordinator.service enabled lava-publisher.service enabled lava-scheduler.service enabled lava-server-gunicorn.service enabled lava-worker.service enabled root@LavaServer:/#root@LavaServer:/#* On Worker following services are enabled after upgrade:(2020.10) *lava@alif-blr-worker02:~$ systemctl list-unit-files | grep enabled |grep lavalava-worker.service enabled * Another Worker which is not upgraded to 2020.10 :(It is running with 2020.08) *Following services are Enabled * *root@alif-blr-worker03:/# systemctl list-unit-files | grep enabled |grep lavalava-coordinator.service enabled lava-logs.service enabled lava-master.service enabled lava-publisher.service enabled lava-server-gunicorn.service enabled lava-slave.service enabled root@alif-blr-worker03:/# * *I am getting this issue with 2020.10 . I haven't seen this issue with previous version upgrades. * Kindly help me out to solve this issue!! Thanks!! Regards Nagendra S

5 years, 4 months

1
0
0 0

"lava-master.log" time stamp does not match to my LAVA "Debian" server time

by koti koti

Hi, It looks like my "lava-master.log ("/var/log/lava-server/lava-master.log)"" (even other lava logs) timestamp does not match to the lava installed server (Debain 10/Buster) time stamp. Do I need to run any command to make sure "lava server logs" timestamp sync with Lava server time stamp? output: ##################### Debian Time: ########### lavamaster@lavamaster:/var/log/lava-server$ date Tue Dec 1 17:37:59 IST 2020 lavamaster@lavamaster:/var/log/lava-server$ lava-master.log: ############# lavamaster@lavamaster:/var/log/lava-server$ tail -f lava-master.log 2020-12-01 12:02:51,507 DEBUG - qemu 2020-12-01 12:02:51,531 DEBUG lava-logs => PING(20) 2020-12-01 12:02:54,519 DEBUG lavamaster => PING(20) 2020-12-01 12:02:58,749 DEBUG raspberrypi => PING(20) 2020-12-01 12:03:11,534 INFO scheduling health checks: 2020-12-01 12:03:11,554 INFO scheduling jobs: 2020-12-01 12:03:11,556 DEBUG - qemu 2020-12-01 12:03:11,582 DEBUG lava-logs => PING(20) 2020-12-01 12:03:14,542 DEBUG lavamaster => PING(20) 2020-12-01 12:03:18,774 DEBUG raspberrypi => PING(20) 2020-12-01 12:03:31,582 INFO scheduling health checks: 2020-12-01 12:03:31,603 INFO scheduling jobs: 2020-12-01 12:03:31,605 DEBUG - qemu 2020-12-01 12:03:31,633 DEBUG lava-logs => PING(20) 2020-12-01 12:03:34,566 DEBUG lavamaster => PING(20) Regards, Koti

5 years, 4 months

2
2
0 0

How can I upgrade my Lava software to latest version (may be 2020.10)

by koti koti

Hi, Recently I have installed Lava-Master and Lava-Dispatcher using the steps mentioned below in the corresponding servers. Server: ###### 1. #sudo install lava Worker (Dispatcher) ################### 1. #sudo install lava-dispatcher But the installeve Lava software version is the old version (*2019.01-5*). Now I want to upgrade to latest (*may be 2020.10*) lava ( https://git.lavasoftware.org/lava/lava/-/tags) Please can someone let me know the steps to upgrade my lava version to the latest? Regards, Koti

5 years, 4 months

2
1
0 0

QEMU "Health-check" job still in running state on my first Remote Worker

by koti koti

Hi, Recently I have installed "LAVA-Master" on Server and "LAVA-Worker (On Remote location)" on Raspberrypi-4 (8GB). Installation steps: ############################### ############################### Server: ###### 1. #sudo install lava Worker (Raspberrypi-4) ################### 1. #sudo install lava-dispatcher Add worker to Master ############################### ############################### 1. sudo lava-server manage device-types add qemu 2. sudo lava-server manage devices add --device-type qemu --worker raspberrypi qemu-02 3. Now I am able to see "raspberrypi" worker in green colour state in the master under "LAVA--->Scheduler-->workers". Problem/issue: ############ 1. My QEMU job(Health-check) is still in running state even after 2 days (Attached the screenshot) even though it is working if my dispatcher is from the same master server. I feels something I missed here and may be extra setups to establish proper communication between "Master" and "Remote-Worker" Please can someone suggest me as what am I missing to complete my QEMU job(Health-check) while it running in "Remote-Worker" ? Regards, Koti

5 years, 4 months

1
1
0 0

Can't find serial port when test.

by cnspring2002

Dear all, I have one issue when use one qualcomn's development board: - test: definitions: - from: inline name: auto_test path: inline/auto_test.yaml repository: metadata: description: run format: Lava-Test name: run run: steps: - lava-test-case "Android_Serial_Case" --shell "./test.py" docker: image: myimage local: true timeout: minutes: 1600 The test.py is from our customer, when run it, it show the error: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/serial/serialposix.py", line 265, in open self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK) FileNotFoundError: [Errno 2] No such file or directory: '/dev/ttyUSB0' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python3.7/site-packages/serial/serialutil.py", line 240, in __init__ self.open() File "/usr/local/lib/python3.7/site-packages/serial/serialposix.py", line 268, in open raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg)) serial.serialutil.SerialException: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0' I have linked the board to pc, and can see the "/dev/ttyUSB0" in my pc, what happened here?

5 years, 4 months

2
3
0 0

What's the suggestion for application which may need fuse in docker test shell?

by Larry Shen

Hi, We have a test which may need /dev/fuse when run in docker test shell, something like next: docker run -it --cap-add SYS_ADMIN --device /dev/fuse --security-opt apparmor:unconfined hello What's the suggestion for this case? Thanks.

5 years, 4 months

1
0
0 0

Moving boot commands from definition to device for UUU boot action

by Westermann, Oliver

Hey, I would like some advice on properly cleaning up my lava jobs. Following some examples, I now have job definitions that work for me. Each job definition contains a path to all images and the full list of boot commands, which are specific to our image setup and therefore ~40 lines, examples below. I would like to separate the boot commands into the device definition as those should stay stable and we only want to test the image files in the job. I've tried to move the -boot section to both the device definitions or the device type definition, but I did not manage to get a working boot out of that setup. If you would like to know what exactly I tried or need additional debug info, let me know. I've added @larry.shen@nxp.com as to my understanding he implemented the UUU actions, so maybe he has some good advice on best practices? Looking forward for some feedback and of cause thanks for the awesome piece of software to the developers! Best regards, Olli Example: actions: - deploy: to: uuu images: boot: url: file:///network-share/imx-boot.uuu initrd: url: file:///network-share/fitImage-fsl-image-mfgtool.bin [4 more image files] - boot: method: uuu commands: # Load SPL and U-Boot - SDP: boot -f {boot} - SDPU: delay 1000 - SDPU: write -f {boot} -offset 0x57c00 - SDPU: jump # run mfgtool ramdisk - FB: ucmd setenv fastboot_buffer ${loadaddr} - FB: download -f {initrd} [ 30 more commands ]

5 years, 4 months

2
3
0 0

Re: [Lava-users] lava-docker-worker: docker OCI runtime error

by K R, ANANTHA

Hi, I had installed docker long back and therefore not remember how I installed it exactly but I think I used "apt-get install docker.io" Here is the docker version running on my system. anantha@anantha-buster:~$ docker version Client: Version: 18.09.1 API version: 1.39 Go version: go1.11.6 Git commit: 4c52b90 Built: Sun, 14 Jun 2020 22:12:29 +0200 OS/Arch: linux/amd64 Experimental: false Server: Engine: Version: 18.09.1 API version: 1.39 (minimum version 1.12) Go version: go1.11.6 Git commit: 4c52b90 Built: Sun Jun 14 20:12:29 2020 OS/Arch: linux/amd64 Experimental: false Full log: https://paste.debian.net/1170559/ Will try with a fresh docker installation as in https://staging.validation.linaro.org/static/docs/v2/docker-admin.html#prer… From: K R, ANANTHA Sent: 06 November 2020 18:08 To: 'lava-users(a)lists.lavasoftware.org' <lava-users(a)lists.lavasoftware.org> Subject: RE: lava-docker-worker: docker OCI runtime error Hi all, I removed the "-init" flag passed to docker command in the /usr/lib/python3/dist-packages/docker_worker.py. After this the worker container started and is shown to be online in lava server web interface. Is this work around ok to be used ? I'm using the lava-docker-worker on a Debian buster (10.6) machine. Thank you, Anantha From: K R, ANANTHA Sent: 04 November 2020 20:37 To: 'lava-users(a)lists.lavasoftware.org' <lava-users(a)lists.lavasoftware.org<mailto:lava-users@lists.lavasoftware.org>> Subject: lava-docker-worker: docker OCI runtime error Hi All, This is my first post in lava support community. I was trying to setup worker using lava-docker-worker. Followed steps as documented here https://git.lavasoftware.org/lava/lava/-/blob/2020.09/doc/content/admin/adv… However I'm stuck with the error from docker daemon as shown in the bellow log. anantha@anantha-buster:~$ sudo lava-docker-worker -l DEBUG --url http://<My-LAVA-server-IP<http://%3cMy-LAVA-server-IP>> 2020.10: Pulling from lavasoftware/lava-dispatcher bb79b6b2107f: Pull complete 81b92962f1c3: Pull complete e69bdb4eac16: Pull complete Digest: sha256:27b3c2a84684bb0705e300899084bcbfcad99bc1fc1fd7917d8bec5ee47d57cb Status: Downloaded newer image for lavasoftware/lava-dispatcher:2020.10 docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. ^c Need help in regard to solve the above error. Thank you, Anantha

5 years, 4 months

1
0
0 0

Re: [Lava-users] lava-docker-worker: docker OCI runtime error

by K R, ANANTHA

Hi all, I removed the "-init" flag passed to docker command in the /usr/lib/python3/dist-packages/docker_worker.py. After this the worker container started and is shown to be online in lava server web interface. Is this work around ok to be used ? I'm using the lava-docker-worker on a Debian buster (10.6) machine. Thank you, Anantha From: K R, ANANTHA Sent: 04 November 2020 20:37 To: 'lava-users(a)lists.lavasoftware.org' <lava-users(a)lists.lavasoftware.org> Subject: lava-docker-worker: docker OCI runtime error Hi All, This is my first post in lava support community. I was trying to setup worker using lava-docker-worker. Followed steps as documented here https://git.lavasoftware.org/lava/lava/-/blob/2020.09/doc/content/admin/adv… However I'm stuck with the error from docker daemon as shown in the bellow log. anantha@anantha-buster:~$ sudo lava-docker-worker -l DEBUG --url http://<My-LAVA-server-IP<http://%3cMy-LAVA-server-IP>> 2020.10: Pulling from lavasoftware/lava-dispatcher bb79b6b2107f: Pull complete 81b92962f1c3: Pull complete e69bdb4eac16: Pull complete Digest: sha256:27b3c2a84684bb0705e300899084bcbfcad99bc1fc1fd7917d8bec5ee47d57cb Status: Downloaded newer image for lavasoftware/lava-dispatcher:2020.10 docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. ^c Need help in regard to solve the above error. Thank you, Anantha

5 years, 5 months

2
1
0 0

lava-docker-worker: docker OCI runtime error

by K R, ANANTHA

Hi All, This is my first post in lava support community. I was trying to setup worker using lava-docker-worker. Followed steps as documented here https://git.lavasoftware.org/lava/lava/-/blob/2020.09/doc/content/admin/adv… However I'm stuck with the error from docker daemon as shown in the bellow log. anantha@anantha-buster:~$ sudo lava-docker-worker -l DEBUG --url http://<My-LAVA-server-IP> 2020.10: Pulling from lavasoftware/lava-dispatcher bb79b6b2107f: Pull complete 81b92962f1c3: Pull complete e69bdb4eac16: Pull complete Digest: sha256:27b3c2a84684bb0705e300899084bcbfcad99bc1fc1fd7917d8bec5ee47d57cb Status: Downloaded newer image for lavasoftware/lava-dispatcher:2020.10 docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. ^c Need help in regard to solve the above error. Thank you, Anantha

5 years, 5 months

1
0
0 0

Re: [Lava-users] lava-docker-worker: how to customize?

by Philippe Mazet (OSS)

Thanks Milosz. Does that mean that a lava-docker-worker is designed to only run jobs which use "docker"? I would not like to modify all my legacy jobs which do not use the new "docker" thing. Also, I understood that this new "docker" in LAVA jobs was mainly aimed at Android testing. For Linux/yocto, that sounds like useless extra complexity (unless I miss something). -----Original Message----- From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of Milosz Wasilewski Sent: Thursday, October 29, 2020 11:03 AM To: Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> Cc: lava-users(a)lists.lavasoftware.org <lava-users(a)lavasoftware.org> Subject: [EXT] Re: [Lava-users] lava-docker-worker: how to customize? Caution: EXT Email On Thu, 29 Oct 2020 at 10:00, Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> wrote: > > Hi All, > > I was exploring the new lava-docker-worker released with 2020.09. > It is pretty handy to start a slave, but I am wondering how to customize the slave image: > I need to add inside my own tools (like uuu), config files (like ser2net.conf), and also install additional packages. > How do you do this on your side? I think you're confusing 2 things here. The lava-docker-worker image is not supposed to run the jobs. For that you use 'docker: <image name>: in the job definition actions. This is the image that should contain flashing tools like uuu. As for ser2net I'm not sure what is the recommendation (Antonio, could you comment?). We're stil using host based ser2net. milosz > > Finally, I noticed that if I don't do a "service tftpd-hpa restart", TFTP does not work. Is it a known issue? > > Thanks, > > Philippe Mazet > > _______________________________________________ > Lava-users mailing list > Lava-users(a)lists.lavasoftware.org > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist > s.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=04%7C01% > 7Cphilippe.mazet%40nxp.com%7Cde6159fe8c1e43cfcc0008d87bf1f211%7C686ea1 > d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637395626367151208%7CUnknown%7CTW > FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6 > Mn0%3D%7C3000&sdata=gElRt2xv5DouqTeQUF6nPlP33MUKUs68ZT8LWmB67%2Fc% > 3D&reserved=0 _______________________________________________ Lava-users mailing list Lava-users(a)lists.lavasoftware.org https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lav…

5 years, 5 months

2
2
0 0

lava-docker-worker: how to customize?

by Philippe Mazet (OSS)

Hi All, I was exploring the new lava-docker-worker released with 2020.09. It is pretty handy to start a slave, but I am wondering how to customize the slave image: I need to add inside my own tools (like uuu), config files (like ser2net.conf), and also install additional packages. How do you do this on your side? Finally, I noticed that if I don't do a "service tftpd-hpa restart", TFTP does not work. Is it a known issue? Thanks, Philippe Mazet

5 years, 5 months

2
1
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users