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