lava-users December 2020

lava-users@lists.lavasoftware.org

8 participants
16 discussions

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

3 years, 1 month

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

3 years, 2 months

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

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

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

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

3 years, 2 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.

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

3 years, 2 months

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

by Nagendra Singamsetti

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

3 years, 4 months

LAVA apt install packages

by Philippe Mazet (OSS)

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

3 years, 4 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users December 2020