lava-users

lava-users@lists.lavasoftware.org

946 discussions

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]

5 years

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.

5 years, 1 month

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!

5 years, 1 month

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

5 years, 1 month

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

5 years, 1 month

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.

5 years, 1 month

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

5 years, 1 month

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.

5 years, 1 month

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.

5 years, 1 month

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

5 years, 1 month

← Newer
1
...
17
18
19
20
21
22
23
...
95
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users