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

by Hedy Lamarr

Dear all, I don't know what operation I have done, but when a device does not have any running job, I still see the device is in running status. I just saw this 1 time, maybe it's a bug or just bad luck. Anyway, I can't reproduce it on other devices, so it's ok. But, could you teach me to reset the status to make the device work again? Do we have some method to reset the status from "Running" to "Idle", or any api if we don't have an interface on the UI? [image: image.png] Thanks, Hedy Lamarr

3 years, 11 months

2
5
0 0

Unable to get kernel boot messages in to lava job while using lava framework & telnet

by Nagendra Singamsetti

Hi , I am trying to automate the linux boot functionality on my custom boards using LAVA framework. Previously I have done it on Renesas board using LAVA it works fine.I got linux boot messages on lava job whereas i am not getting with customised board. *Issue: *I am using trace32 debugger to flash images onto the board (working fine). After that i am calling minimal method in pipeline job to get prompt strings/login But i am not getting the linux boot messages on the job. always stucks at the following: [common] connect-device Connecting to device using 'telnet 10.10.0.18 4000' <http://10.10.0.69/scheduler/job/789#L136>Setting prompt string to ['lava-test: # '] <http://10.10.0.69/scheduler/job/789#L137>end: 2.3 connect-device (duration 00:00:00) [common] <http://10.10.0.69/scheduler/job/789#L138>end: 2 boot-trace32-image (duration 00:00:28) [common] <http://10.10.0.69/scheduler/job/789#action_3>start: 3 minimal-boot (timeout 00:03:00) [common] <http://10.10.0.69/scheduler/job/789#action_3-1>start: 3.1 connect-device (timeout 00:03:00) [common] <http://10.10.0.69/scheduler/job/789#L141>Already connected <http://10.10.0.69/scheduler/job/789#L142>end: 3.1 connect-device (duration 00:00:00) [common] <http://10.10.0.69/scheduler/job/789#action_3-2>start: 3.2 auto-login-action (timeout 00:03:00) [common] <http://10.10.0.69/scheduler/job/789#L144>Setting prompt string to ['Booting Linux'] <http://10.10.0.69/scheduler/job/789#L145>auto-login-action: Wait for prompt ['Booting Linux'] (timeout 00:03:00) <http://10.10.0.69/scheduler/job/789#L146>Trying 10.10.0.18... <http://10.10.0.69/scheduler/job/789#L147>Connected to 10.10.0.18. <http://10.10.0.69/scheduler/job/789#L148>Escape character is '^]'. <http://10.10.0.69/scheduler/job/789#L149> <http://10.10.0.69/scheduler/job/789#L150>alif_asic01 4000 [115200 N81] <http://10.10.0.69/scheduler/job/789#L151> <http://10.10.0.69/scheduler/job/789#L152>auto-login-action timed out after 180 seconds <http://10.10.0.69/scheduler/job/789#L153>end: 3.2 auto-login-action (duration 00:03:00) [common] *Both telnet & serial server(ser2net) is configured.* *Uart cable attached with serial server: usb-Profolic_Technology_Inc._Usb-serial_Controller-ifoo-port0* i am getting boot log messages using telnet manually but not with lava. *Manual log with telnet:* $ telnet 10.10.0.18 4000 Trying 10.10.0.18... Connected to 10.10.0.18. Escape character is '^]'. alif_asic01 4000 [115200 N81] Booting Linux on physical CPU 0x0 Linux version 5.4.25-00024-g9283a6810958-dirty (nishit@alif) (gcc version 9.2.0 (GCC)) #72 Tue Apr 20 15:41:31 IST 2021 #HGG1 CPU: ARMv8-a aarch32 Processor [411fd010] revision 0 (ARMv8), cr=50c5383d CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache #HGG1.1 OF: fdt: Machine model: corstone700 [PFA] yaml job thanks Regards Nagendra S

3 years, 11 months

2
1
0 0

About serial question.

by Hedy Lamarr

Dear, Recently I'm learning and evaluating LAVA to see if it can help us. I saw next from https://validation.linaro.org/static/docs/v2/connections.html: {% set connection_list = ['uart0', 'uart1'] %}{% set connection_commands = {'uart0': 'telnet dispatcher01 7001', 'uart1': 'telnet dispatcher01 7002'} %} I'm pretty confused by the 'uart0', 'uart1'. Should I explicitly specify something in my job to let some action to choose 'uart0' or 'uart1'? How does LAVA know at which time it should choose which uart? Thanks, Hedy Lamarr

3 years, 11 months

2
2
0 0

IRC status

by Corentin Labbe

Hello Since freenode is doing strange stuff (to remains polite) against users, do you have a plan to migrate #lavasoftware away off freenode ? Regards

3 years, 11 months

2
2
0 0

iso-installer for ubuntu 20.04

by Moein Shafi

Hello everyone, I'm new to LAVA and I have some issue with 'iso-installer' for ubuntu 20.04 . As you know, in ubuntu 20.04 the preseed file would not use 'debian_installer' and use 'subiquity' instead, Also LAVA does not support 'subiquity' for 'iso-installer', so I don't know how can I use 'iso-installer' for testing my ubuntu 20.04.

3 years, 11 months

2
1
0 0

About lkft.

by Hedy Lamarr

Dear, I saw https://lkft.linaro.org/ by chance, I wonder if we could benefit from this on our android test? Does it already have any kernel test for android kernel? Thanks, Hedy Lamarr

3 years, 11 months

2
4
0 0

Pending merge requests

by Philippe Mazet (OSS)

Hello LAVA maintainers, We have some MRs pending in https://git.lavasoftware.org/lava/lava/-/merge_requests Some of them for many weeks. Please let us know if there is anything we could do to help get them reviewed. Thank you very much in advance for your feedback. Philippe Examples: https://git.lavasoftware.org/lava/lava/-/merge_requests/1441 https://git.lavasoftware.org/lava/lava/-/merge_requests/1469 https://git.lavasoftware.org/lava/lava/-/merge_requests/1324 ...

3 years, 11 months

2
1
0 0

Docker-compose setup broken by 2021.04

by Westermann, Oliver

Hey, By coincidence I setup a local test instance of the lava docker-compose setup. I usually use merge master regularly, so my .env file contained DC_SERVER_IMAGE=lavasoftware/lava-server:latest. When I started this up, I get > lava-publisher_1 | ModuleNotFoundError: No module named 'environ' in the logs from various containers based upon lava-server. I tested it on my production setup as well as tested fixing my revision to 2021.03.post1, which fixes this. I checked my changes to the setup and couldn't find anything that looks related, so maybe consider this a bug report? Full callstack below, best regards Oliver Westermann Full Error Log: lava-publisher_1 | Traceback (most recent call last): lava-publisher_1 | File "/usr/share/lava-server/postinst.py", line 326, in <module> lava-publisher_1 | sys.exit(main()) lava-publisher_1 | File "/usr/share/lava-server/postinst.py", line 263, in main lava-publisher_1 | config = load_configuration() lava-publisher_1 | File "/usr/share/lava-server/postinst.py", line 127, in load_configuration lava-publisher_1 | module = importlib.import_module("lava_server.settings.prod") lava-publisher_1 | File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module lava-publisher_1 | return _bootstrap._gcd_import(name[level:], package, level) lava-publisher_1 | File "<frozen importlib._bootstrap>", line 1006, in _gcd_import lava-publisher_1 | File "<frozen importlib._bootstrap>", line 983, in _find_and_load lava-publisher_1 | File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked lava-publisher_1 | File "<frozen importlib._bootstrap>", line 677, in _load_unlocked lava-publisher_1 | File "<frozen importlib._bootstrap_external>", line 728, in exec_module lava-publisher_1 | File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed lava-publisher_1 | File "/usr/lib/python3/dist-packages/lava_server/settings/prod.py", line 23, in <module> lava-publisher_1 | import environ lava-publisher_1 | ModuleNotFoundError: No module named 'environ'

4 years

3
2
0 0

Error updating to 2021.04

by Tim Jaacks

Hello everyone, I just wanted to update to LAVA 2021.04, but encountered the following error on 'apt-get update': Reading package lists... Done E: The repository 'https://apt.lavasoftware.org/release buster Release' is no longer signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. Is this a problem on your side? I have installed the production key, and updates used to work in the past. Best regards, Tim -- Tim Jaacks SOFTWARE DEVELOPER Garz & Fricke GmbH Schlachthofstrasse 20 21079 Hamburg T: +49 40 791899-183 E: tim.jaacks(a)garz-fricke.com WE MAKE IT YOURS! Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Stefan Heczko, Matthias Fricke, Marc-Michael Braun

4 years

2
1
0 0

Unable to get kernel boot messages in to lava job while using lava framework & telnet

by koti

Hi Nagendra, I suspect the auto-login action functionality. Please try to test by avoiding auto-login functionality. We can nail down/avoid the auto-login functionality issue like below. Steps: ###### 1. Boot the target manually and login 2. Make sure you will get login prompt 3. Run reset/reboot command 4. Check whether we will get to see the console log in the LAVA result page. Best of luck! Note: 1. You can use below "-boot" section " - boot: timeout: minutes: 2 method: minimal soft_reboot: ["reset;pwd;reset"] parameters: shutdown-message: ["< Please mention shutdown message > "] boot-message: [" < Please mention boot message "] " Regards, Koti On Thu, 22 Apr 2021 at 21:33, <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. Unable to get kernel boot messages in to lava job while using > lava framework & telnet (Nagendra Singamsetti) > 2. Notify on finish does not hold duration (Westermann, Oliver) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 22 Apr 2021 17:53:31 +0530 > From: Nagendra Singamsetti <nag.singam91(a)gmail.com> > To: lava-users(a)lists.lavasoftware.org > Subject: [Lava-users] Unable to get kernel boot messages in to lava > job while using lava framework & telnet > Message-ID: > <CAFhg_Wste+2=zO51aA3GOq-BjwbUx76rms= > gF8Rv-hKNCOeQVQ(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi , > > I am trying to automate the linux boot functionality on my custom boards > using LAVA framework. Previously I have done it on Renesas board using LAVA > it works fine.I got linux boot messages on lava job whereas i am not > getting with customised board. > > *Issue: *I am using trace32 debugger to flash images onto the board > (working fine). After that i am calling minimal method in pipeline job to > get prompt strings/login > But i am not getting the linux boot messages on the job. always stucks at > the following: > [common] connect-device Connecting to device using 'telnet 10.10.0.18 4000' > <http://10.10.0.69/scheduler/job/789#L136>Setting prompt string to > ['lava-test: # '] <http://10.10.0.69/scheduler/job/789#L137>end: 2.3 > connect-device (duration 00:00:00) [common] > <http://10.10.0.69/scheduler/job/789#L138>end: 2 boot-trace32-image > (duration 00:00:28) [common] > <http://10.10.0.69/scheduler/job/789#action_3>start: > 3 minimal-boot (timeout 00:03:00) [common] > <http://10.10.0.69/scheduler/job/789#action_3-1>start: 3.1 connect-device > (timeout 00:03:00) [common] <http://10.10.0.69/scheduler/job/789#L141 > >Already > connected <http://10.10.0.69/scheduler/job/789#L142>end: 3.1 > connect-device > (duration 00:00:00) [common] > <http://10.10.0.69/scheduler/job/789#action_3-2>start: 3.2 > auto-login-action (timeout 00:03:00) [common] > <http://10.10.0.69/scheduler/job/789#L144>Setting prompt string to > ['Booting Linux'] <http://10.10.0.69/scheduler/job/789#L145 > >auto-login-action: > Wait for prompt ['Booting Linux'] (timeout 00:03:00) > <http://10.10.0.69/scheduler/job/789#L146>Trying 10.10.0.18... > <http://10.10.0.69/scheduler/job/789#L147>Connected to 10.10.0.18. > <http://10.10.0.69/scheduler/job/789#L148>Escape character is '^]'. > <http://10.10.0.69/scheduler/job/789#L149> > <http://10.10.0.69/scheduler/job/789#L150>alif_asic01 4000 [115200 N81] > <http://10.10.0.69/scheduler/job/789#L151> > <http://10.10.0.69/scheduler/job/789#L152>auto-login-action timed out > after > 180 seconds <http://10.10.0.69/scheduler/job/789#L153>end: 3.2 > auto-login-action (duration 00:03:00) [common] > > *Both telnet & serial server(ser2net) is configured.* > *Uart cable attached with serial server: > usb-Profolic_Technology_Inc._Usb-serial_Controller-ifoo-port0* > > i am getting boot log messages using telnet manually but not with lava. > > *Manual log with telnet:* > $ telnet 10.10.0.18 4000 > Trying 10.10.0.18... > Connected to 10.10.0.18. > Escape character is '^]'. > > alif_asic01 4000 [115200 N81] > > Booting Linux on physical CPU 0x0 > Linux version 5.4.25-00024-g9283a6810958-dirty (nishit@alif) (gcc version > 9.2.0 (GCC)) #72 Tue Apr 20 15:41:31 IST 2021 > #HGG1 > CPU: ARMv8-a aarch32 Processor [411fd010] revision 0 (ARMv8), cr=50c5383d > CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache > #HGG1.1 > OF: fdt: Machine model: corstone700 > > [PFA] yaml job > > thanks > > Regards > Nagendra S >

4 years

1
0
0 0

Notify on finish does not hold duration

by Westermann, Oliver

Hey, I'm using the 'notify by mail' option for our setup. It's setup as criteria: status: finished But when the mail is send, it seems the the job is not really finished yet, as the mail do contain timestamps for submitted and started, but not for finished. This also results in Duration being None. Also I noticed that the "Device Details" and "Job Details" elements are empty for me. Is this "expected" behavior or is my setup wrong? (Using LAVA 2021.03.post1, but existed on 2021.1 as well) Best regards, Olli

4 years

1
0
0 0

How /dev/log could be seen in lava docker slave?

by Larry Shen

Hi, guys, I have a question related to udev share: The logger of lava dispatcher host was configured as "/dev/log", which link to "/dev/log -> /run/systemd/journal/dev-log". How could I see them in lava docker slave? (Not native Debian slave). Thanks.

4 years

1
1
0 0

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

by Philippe Mazet (OSS)

Ok. You get 2 MRs for the price of one : In docker-compose tree: https://git.lavasoftware.org/lava/pkg/docker-compose/-/merge_requests/37 In LAVA documentation: https://git.lavasoftware.org/lava/lava/-/merge_requests/1479 May I ask an update about our other pending MRs? ;-) Thanks a lot in advance, Philippe From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of Remi Duraffort Sent: Wednesday, April 14, 2021 9:20 AM To: Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> Cc: lava-users(a)lists.lavasoftware.org <lava-users(a)lavasoftware.org> Subject: Re: [Lava-users] LAVA master backup/restore Hello, if you have some time, a patch to update the documentation would be greatly appreciated !! Thanks a lot. Le ven. 2 avr. 2021 à 11:34, Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> a écrit : Hi Rémi, I finally found this to work: For creating the backup, run backup command as postgres user, eg: docker exec --user postgres docker-compose_db_1 bash -c "pg_dump --username=lavaserver lavaserver > /var/lib/postgresql/data/lavaserver.sql" Then for restoring backup, place the sql file in a folder that will be mounted as a volume in postgres container, on /docker-entrypoint-initdb.d/. On way to do this is to create a dedicated docker-compose file (docker-compose-restore-backup.yaml) that will be appended to docker-compose.yaml: version: "3.4" services: db: volumes: - ./initdb.d:/docker-entrypoint-initdb.d Then: docker-compose stop docker container rm docker-compose_db_1; docker volume rm lava-server-pgdata docker-compose -f docker-compose.yaml -f docker-compose-restore-backup.yaml up -d I hope that helps. Philippe From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of Remi Duraffort Sent: Friday, March 26, 2021 4:56 PM To: Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> Cc: lava-users(a)lists.lavasoftware.org <lava-users(a)lavasoftware.org> Subject: Re: [Lava-users] LAVA master backup/restore Hello Philippe, I haven't tried so I don't have the detailed procedure. When you find out, could you share the procedure ? Thanks Le mar. 23 mars 2021 à 11:28, Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> a écrit : Thanks Rémi, but result is the same when I start only the db container, even after a full cleanup (docker container rm docker-compose_db_1 && docker volume rm lava-server-pgdata): ERROR: database "lavaserver" already exists Seems to be related somehow to "POSTGRES_USER: lavaserver" in docker-compose.yaml. Reading the entrypoint script for postgres (https://github.com/docker-library/postgres/blob/master/docker-entrypoint.sh), I thought using PGUSER could help, but I didn't manage yet to get that working. I will continue digging into this... but if you have a detailed procedure somewhere, please share 😊 Thanks a lot! Philippe From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of Remi Duraffort Sent: Monday, March 22, 2021 9:25 AM To: Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> Cc: lava-users(a)lists.lavasoftware.org <lava-users(a)lavasoftware.org> Subject: Re: [Lava-users] LAVA master backup/restore Le jeu. 18 mars 2021 à 16:22, Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> a écrit : 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? I guess that's only because lava will automatically create an empty lavaserver database. So in your use case, you should only start the db service and not any lava-* services. When the restoration has been done, you can restart every lava services. - 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 _______________________________________________ Lava-users mailing list Lava-users(a)lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users -- Rémi Duraffort LAVA Architect Linaro -- Rémi Duraffort LAVA Architect Linaro -- Rémi Duraffort TuxArchitect Linaro

4 years

1
0
0 0

LAVA exporting bash shell while using debian OS parameter

by P T, Sarath

Hi Team, I have used the LAVA job definition including deployment data(OS parameter) as debian . As per the deployment_data.py it should export the shell as /bin/bash but it's exporting /bin/sh. I am observing this thing after updating LAVA to 2021.01. Below I am giving the job definition file which I used. It will be very helpful if anyone reply on this. Thank you . Job definition ============= device_type: x86-simatic-slll job_name: x86-simatic-ipc227e-slll health-check timeouts: job: minutes: 20 action: minutes: 20 connection: minutes: 10 priority: medium visibility: public tags: - slll-simatic-ipc-227e-01 actions: - deploy: to: overlay - boot: method: minimal reset: true failure_retry: 2 auto_login: login_prompt: 'ebsy-isar login:' username: root password_prompt: 'Password:' password: root prompts: - root@ebsy-isar:~# transfer_overlay: download_command: wget unpack_command: tar -C / -xzf # TEST_BLOCK - test: timeout: minutes: 5 definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: kernel-version-basic description: "check kernel version" os: - debian scope: - functional run: steps: - lava-test-case uname --shell uname -a from: inline name: kernel-version-inline path: inline/kernel-version-basic.yaml lava-signal: kmsg Regards Sarath P T

4 years

2
2
0 0

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

by Philippe Mazet (OSS)

Hi Rémi, I finally found this to work: For creating the backup, run backup command as postgres user, eg: docker exec --user postgres docker-compose_db_1 bash -c "pg_dump --username=lavaserver lavaserver > /var/lib/postgresql/data/lavaserver.sql" Then for restoring backup, place the sql file in a folder that will be mounted as a volume in postgres container, on /docker-entrypoint-initdb.d/. On way to do this is to create a dedicated docker-compose file (docker-compose-restore-backup.yaml) that will be appended to docker-compose.yaml: version: "3.4" services: db: volumes: - ./initdb.d:/docker-entrypoint-initdb.d Then: docker-compose stop docker container rm docker-compose_db_1; docker volume rm lava-server-pgdata docker-compose -f docker-compose.yaml -f docker-compose-restore-backup.yaml up -d I hope that helps. Philippe From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of Remi Duraffort Sent: Friday, March 26, 2021 4:56 PM To: Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> Cc: lava-users(a)lists.lavasoftware.org <lava-users(a)lavasoftware.org> Subject: Re: [Lava-users] LAVA master backup/restore Hello Philippe, I haven't tried so I don't have the detailed procedure. When you find out, could you share the procedure ? Thanks Le mar. 23 mars 2021 à 11:28, Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> a écrit : Thanks Rémi, but result is the same when I start only the db container, even after a full cleanup (docker container rm docker-compose_db_1 && docker volume rm lava-server-pgdata): ERROR: database "lavaserver" already exists Seems to be related somehow to "POSTGRES_USER: lavaserver" in docker-compose.yaml. Reading the entrypoint script for postgres (https://github.com/docker-library/postgres/blob/master/docker-entrypoint.sh), I thought using PGUSER could help, but I didn't manage yet to get that working. I will continue digging into this... but if you have a detailed procedure somewhere, please share 😊 Thanks a lot! Philippe From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of Remi Duraffort Sent: Monday, March 22, 2021 9:25 AM To: Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> Cc: lava-users(a)lists.lavasoftware.org <lava-users(a)lavasoftware.org> Subject: Re: [Lava-users] LAVA master backup/restore Le jeu. 18 mars 2021 à 16:22, Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> a écrit : 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? I guess that's only because lava will automatically create an empty lavaserver database. So in your use case, you should only start the db service and not any lava-* services. When the restoration has been done, you can restart every lava services. - 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 _______________________________________________ Lava-users mailing list Lava-users(a)lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users -- Rémi Duraffort LAVA Architect Linaro -- Rémi Duraffort LAVA Architect Linaro

4 years

2
1
0 0

Re: [Lava-users] Worker/master version mismatch

by Philippe Mazet (OSS)

I have submitted a MR to allow version mismatch: https://git.lavasoftware.org/lava/lava/-/merge_requests/1466 This feature is really a *must-have* for us. At our own risks of course. Thanks for considering it! We also have quite a few other MRs in the pipe. Some of them are few months old, even if all comments are replied. What is the appropriate way to get them reviewed/merged? ;-) Thanks a lot, Philippe From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of Remi Duraffort Sent: Tuesday, January 26, 2021 10:04 AM To: Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> Cc: lava-users(a)lists.lavasoftware.org <lava-users(a)lavasoftware.org> Subject: Re: [Lava-users] Worker/master version mismatch Hello Philippe, I tried the lava-docker-worker but found it too restrictive, since we can’t customize the Docker container at all (adding some tools, cfg files, ssh keys, etc…), and was imposing usage of Docker within the job themselves (that would force us to rewrite many of our existing tests). That's an interesting use case. Maybe something that we might want to support. A possibility would be to specify the docker registry that you want to use instead of docker hub. As to “automatically run the right worker version”, I might have missed something. By checking lava-docker-worker sources, I concluded the Docker would simply refuse to start if version differs versus master. But do you mean it will automatically restart with the correct version when master is upgraded? That would be an easy fix (just adding a settings to lava_server and return depending on the setting value). But keep in mind that this might break at any release. Rgds -- Rémi Duraffort LAVA Architect Linaro

4 years

2
1
0 0

We use “run_step” method in lava definitions, but it cannot work when we upgrade lava from 2018.11 stretch to 2021.01

by yangjianxiang

Hi ： We use “run_step” method in lava definitions, but it cannot work when we upgrade lava from 2018.11 stretch to 2021.01. How can we slove this problem. [cid:image001.png@01D73098.D3FE9C80]

4 years

2
2
0 0

About device change permission.

by Larry Shen

Hi, guys, I'm currently debug permission issue on our production master, it looks like next: 1. I set user e.g. "zz" to group "imxcn", and assign device "imx8mm-evk-sh99" with the permission "change_device". But, in our production master, "zz"(not admin), can't change the device status. What's strange is: I have a local master on my hand, on this master, I do the same configure, the non-admin user can change the device status. 2. I check the database of our production master as next; auth_user: 39 | | 2021-03-30 08:37:32.98708+00 | f | zz auth_group: 8 | imxcn auth_user_groups: 290 | 39 | 8 lava_scheduler_app_groupdevicepermission: 91 | imx8mm-evk-sh99 | 8 | 9 92 | imx8mm-evk-sh99 | 8 | 5 auth_permission: 5 | Can submit jobs to device | 2 | submit_to_device 9 | Can change device | 2 | change_device django_content_type: 2 | lava_scheduler_app | device Looks all data is ok, so, base on above data, do you know any possible reason why our production server can't allow non-admin user change device permission? I'm a little lost as my local on hand server works, just central production server not work... Thanks.

4 years, 1 month

1
1
0 0

How to change device healthy using rest api?

by cnspring2002

Hello, LAVA maintainer: I used to use xmlrpc to change the status of our device, now I want to switch to rest api, but I don't know how to handle it with next: https://validation.linaro.org/static/docs/v2/data-export.html#v0-2 It didn't give an example, and also did not specify using GET, POST, PUT or DELETE, could you give an example to me? Like a curl command format. Thank you!

4 years, 1 month

2
1
0 0

Suggestion on avoiding cloning of same repositories multiple times.

by Kumar, Maanas

Hello, We have job definition with multiple test definitions as shown below. test: timeout: hours: 4 definitions: - repository: ssh://git@github.com:7999/<MytestRepo>.git from: git path: automated/linux/lttng/lttng.yaml name: lttng - repository: ssh://git@github.com:7999/<MytestRepo> from: git path: automated/linux/docker/docker.yaml name: docker We want to avoid multiple cloning of same repository as all our test-definitions are in one repo. We require suggestions on how to avoid cloning of same repository multiple times.? Regards, Maanas M D

4 years, 1 month

2
1
0 0

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

by Philippe Mazet (OSS)

Thanks Rémi, but result is the same when I start only the db container, even after a full cleanup (docker container rm docker-compose_db_1 && docker volume rm lava-server-pgdata): ERROR: database "lavaserver" already exists Seems to be related somehow to "POSTGRES_USER: lavaserver" in docker-compose.yaml. Reading the entrypoint script for postgres (https://github.com/docker-library/postgres/blob/master/docker-entrypoint.sh), I thought using PGUSER could help, but I didn't manage yet to get that working. I will continue digging into this... but if you have a detailed procedure somewhere, please share 😊 Thanks a lot! Philippe From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of Remi Duraffort Sent: Monday, March 22, 2021 9:25 AM To: Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> Cc: lava-users(a)lists.lavasoftware.org <lava-users(a)lavasoftware.org> Subject: Re: [Lava-users] LAVA master backup/restore Le jeu. 18 mars 2021 à 16:22, Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> a écrit : 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? I guess that's only because lava will automatically create an empty lavaserver database. So in your use case, you should only start the db service and not any lava-* services. When the restoration has been done, you can restart every lava services. - 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 _______________________________________________ Lava-users mailing list Lava-users(a)lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users -- Rémi Duraffort LAVA Architect Linaro

4 years, 1 month

2
1
0 0

docker support for adb-fastboot

by Marcel Trattner

Dear LAVA-Users, as far as we know the lxc support for LAVA test is going to be depricated and docker should be used instead, so we tried to define a test job with docker. The lxc job for this device was completing but when we tried to follow this tutorial: https://www.youtube.com/watch?v=y-5DjzQztAk with the following test job: timeouts: job: minutes: 30 connection: minutes: 2 actions: finalize: seconds: 60 context: test_character_delay: 10 device_type: dragonboard_845_uSOM job_name: Docker-Test priority: 50 visibility: public metadata: build-url: '' actions: - deploy: to: fastboot docker: image: adb-fastboot timeout: minutes: 15 images: boot: url: https://path/to/image/boot.img reboot: hard-reset - boot: method: fastboot docker: image: adb-fastboot prompts: - root@(.*):/# timeout: minutes: 15 - test: docker: image: adb-fastboot timeout: minutes: 10 definitions: - repository: https://github.com/Linaro/test-definitions.git from: git path: automated/linux/android-platform-tools/install.yaml name: install-android-platform-tools-r2800 parameters: LINK: https://dl.google.com/android/repository/platform-tools_r28.0.0-linux.zip We got this error: [cid:image001.jpg@01D7224A.65849130] Are we doing something wrong or is this a bug? 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.

4 years, 1 month

1
0
0 0

Re: [Lava-users] How many cts could be run parallel in one lava worker?

by Dave Pigott

Hi Larry, That is really underpowered for the sort of work you’re doing. We have a guideline of at least 8 cores and 16GB RAM. With only 4 cores you’re going to run into resource starvation issues. Thanks Dave ---------------- Dave Pigott LAVA Lab Lead Linaro Ltd t: (+44) (0) 1223 400063

4 years, 1 month

1
0
0 0

How many cts could be run parallel in one lava worker?

by Larry Shen

Hi, I'd like to know what's linaro's pc setup for android cts? I ask this question because in one of our pc, if run 3 cts together at the same time, after about 8 hours, some of job' log will hang at web. Check the server log, it looks the lava worker already sent the "END", while lava serer also sent the "END OK", also "description.yaml" received by server which means lava-run not crash. Just there is also one time's END resend, and the job/device still in running status for ever. Looks the zeromq connection to lava-log down? I'm not sure (We still link the device to 2020.08, not sure 2021.03 which don't use zmq helps or not). And, the dmesg keeps tell `docker0: port 3(vethb545eb3) entered disabled state`, so I suspect high resource usage in this pc when test cts may result in some connection issue. Our pc has 8G memory, Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz, 4 cores. What's your suggestion for pc configuration to run parallel cts jobs? Have your ever encountered similar issue? Thanks.

4 years, 1 month

1
0
0 0

Failed Ram Init - Raspberry pi 4

by Gaurav Kumar

Hi Lava user, I complied the stable AGL from gerrit repo. Facing an issue, the init process is failed. I have used the below command to build the ramdisk. mkimage -A arm64 -T ramdisk -C none -d [cid:image001.png@01D71CCC.11853E50] Please suggest what wrong I am doing. Kind Regards, Gaurav Kumar _____________________________________________________________________________________ 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.

4 years, 1 month

2
3
0 0

Re: [Lava-users] Unable to change device health state without being admin

by Sebastien Haezebrouck

I am reopening this old thread – we switched this morning to version 2021.03 – which seems to work just fine. However, the annoying problem mentioned below seems to be still there: without admin rights no one seems to be able to modify the health state of any device, even those who have the proper “can change device” permission for members of our group. Is this something experienced by other people, or just us ? Regards, Seb From: Sebastien Haezebrouck Sent: Thursday, January 28, 2021 7:19 PM To: Remi Duraffort <remi.duraffort(a)linaro.org> Cc: lava-users(a)lists.lavasoftware.org Subject: RE: [EXT] Re: [Lava-users] Unable to change device health state without being admin Hi Remi, Thanks for your answer. * You can restrict view/submit/change permissions per device and per groups. So go into the specific device admin page (something * like https://<instance>/admin/lava_scheduler_app/device/<hostname>/change/<https://%3cinstance%3e/admin/lava_scheduler_app/device/%3chostname%3e/change/>). * At the bottom of the page you will be able to add the restrictions. This is exactly what I had done previously. Adding the “lava_scheduler_app | device | Can change device” permission to our group does not seem to have any effect. Regards, Seb From: Remi Duraffort <remi.duraffort(a)linaro.org<mailto:remi.duraffort@linaro.org>> Sent: Tuesday, January 26, 2021 9:55 AM To: Sebastien Haezebrouck <sebastien.haezebrouck(a)nxp.com<mailto:sebastien.haezebrouck@nxp.com>> Cc: lava-users(a)lists.lavasoftware.org<mailto:lava-users@lists.lavasoftware.org> Subject: [EXT] Re: [Lava-users] Unable to change device health state without being admin Caution: EXT Email Hello, the authorization models changed some time ago. The doc for the new model is here: https://docs.lavasoftware.org/lava/authorization.html<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.lava…> You can restrict view/submit/change permissions per device and per groups. So go into the specific device admin page (something like https://<instance>/admin/lava_scheduler_app/device/<hostname>/change/<https://%3cinstance%3e/admin/lava_scheduler_app/device/%3chostname%3e/change/>). At the bottom of the page you will be able to add the restrictions. Rgds Le jeu. 17 déc. 2020 à 16:47, Sebastien Haezebrouck <sebastien.haezebrouck(a)nxp.com<mailto:sebastien.haezebrouck@nxp.com>> a écrit : 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 _______________________________________________ Lava-users mailing list Lava-users(a)lists.lavasoftware.org<mailto:Lava-users@lists.lavasoftware.org> https://lists.lavasoftware.org/mailman/listinfo/lava-users<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lav…> -- Rémi Duraffort LAVA Architect Linaro

4 years, 1 month

1
0
0 0

Help with Raspberry integration

by Marcel Trattner

Dear LAVA-Team, I'm writing you again, because we are still struggling to get our LAVA infrastructure running. Since the last time we have switched from the more advanced Board to a set of three Raspberry Pis, which we want to test with different Operating Systems to gain more experience in using LAVA. For the configuration of our Raspberry Pi, running Rasbian, we can't quite get past the login and reboot phase. It is connected via serial and integrated with Ser2Net, the device dictionary looks like this now: {% extends 'bcm2711-rpi-4-b.jinja2' %} {% set soft_reboot_command = 'sudo reboot' %} {% set auto_login_prompt = "raspberrypi login:" %} {% set auto_login_username = "pi" %} {% set ssh_host = '192.168.1.11' %} {% set connection_list = ['uart0'] %} {% set connection_commands = {'uart0': 'telnet <HOST IP> 7102'} %} {% set connection_tags = {'uart0': ['primary', 'telnet']} %} In the health check we just want to pull some standard images and deploy them with tftp, then login and run smoke tests by Linaro. The current health job looks like this: device_type: bcm2711-rpi-4-b job_name: RPI-01 (Raspbian) Health Check timeouts: job: minutes: 10 connection: minutes: 2 action: minutes: 10 priority: medium visibility: public actions: - deploy: timeout: minutes: 10 to: tftp kernel: url: https://storage.kernelci.org/mainline/master/v5.11/arm64/defconfig/clang-10… type: image ramdisk: url: https://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05/arm64/base… compression: gz modules: url: https://storage.kernelci.org/mainline/master/v5.11/arm64/defconfig/clang-10… compression: xz dtb: url: https://storage.kernelci.org/mainline/master/v5.11/arm64/defconfig/clang-10… os: oe - boot: timeout: minutes: 2 method: u-boot commands: ramdisk prompts: - 'pi@raspberrypi:~$' auto_login: login_prompt: 'raspberrypi login:' username: pi password_prompt: 'Password:' password: 1234567890 login_commands: - sudo su - test: definitions: - {from: git, name: smoke-tests, path: lava-test-shell/smoke-tests-basic.yaml, repository: 'http://git.linaro.org/lava-team/lava-functional-tests.git'} timeout: {minutes: 5} But with this we are having issues when the DUT is supposed to reboot because we get stuck at the login prompt. First problem is probably the auto_login, we have defined username and password, but for the password definition we get this problem: [cid:image001.png@01D711E1.6A14C9A0] Can you explain, what we are doing wrong? Then LAVA is sending the reboot commands but those always seem to fail at the login. The Error looks somewhat like this: [cid:image002.png@01D711E1.6A14C9A0] Does this have to do with the deployment through tftp or is it the autologin? Also the login and password prompts won't get recognized and are not filled in. Can you tell us, what we are doing wrong? 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.

4 years, 1 month

3
2
0 0

LAVA master backup/restore

by Philippe Mazet (OSS)

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

4 years, 1 month

2
1
0 0

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.

4 years, 1 month

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.

4 years, 1 month

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

4 years, 1 month

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

4 years, 1 month

2
1
0 0

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

by deffo＠gmx.de

4 years, 1 month

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

4 years, 1 month

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

4 years, 1 month

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

4 years, 1 month

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?

4 years, 1 month

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

4 years, 2 months

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 >

4 years, 2 months

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

4 years, 2 months

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

4 years, 2 months

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

4 years, 2 months

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

4 years, 3 months

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]

4 years, 3 months

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

4 years, 3 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]

4 years, 3 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

4 years, 3 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

4 years, 3 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

4 years, 3 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 >

4 years, 3 months

2
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users