lava-users

lava-users@lists.lavasoftware.org

1 participants
948 discussions

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

by koti koti

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

5 years, 4 months

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

by yangjianxiang

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

5 years, 4 months

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

by yangjianxiang

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

5 years, 4 months

Unable to change device health state without being admin

by Sebastien Haezebrouck

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

5 years, 4 months

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

by Anand, Ravi

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

5 years, 4 months

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

by koti koti

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

5 years, 4 months

TR: issue with lava agent installation

by MARVIN Trijasse

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

5 years, 4 months

Worker/master version mismatch

by Philippe Mazet (OSS)

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

5 years, 4 months

Regarding lava installation facing problem

by Satishkumar Rajguru

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

5 years, 4 months

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

by Singamsetty Nagendra

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

5 years, 4 months

← Newer
1
...
20
21
22
23
24
25
26
...
95
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users