lava-users January 2021

lava-users@lists.lavasoftware.org

10 participants
17 discussions

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

by Singamsetty Nagendra

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

3 years, 2 months

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

by yangjianxiang

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

3 years, 2 months

WG: Help with new device integration

by Marcel Trattner

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

3 years, 2 months

Define "Missing key" Whitelist

by Westermann, Oliver

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

3 years, 2 months

Docker transfer_overlays problem

by Seb Seb

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

3 years, 2 months

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

by yangjianxiang

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

3 years, 3 months

Ask android vts test link in docker test shell.

by Larry Shen

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

3 years, 3 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users January 2021