Hi everyone,
I'm experiencing this error on setting up my U-Boot based device:
Unable to extract cpio archive '/var/lib/lava/dispatcher/tmp/17/extract-overlay-ramdisk-tv17mriz/ramdisk.cpio': Command '['cpio', '--extract', '--make-directories', '--unconditional', '--file', '/var/lib/lava/dispatcher/tmp/17/extract-overlay-ramdisk-tv17mriz/ramdisk.cpio']' returned non-zero exit status 2.
As documentation in https://docs.lavasoftware.org/lava/actions-deploy.html#deploy-action-roles states, the overlay will only be used, when a test action is defined in job - so I removed the test action (and the log states "[common] skipped lava-overlay - no test action.") but the error still appears.
For debugging I commented out the _cleanup() function in /usr/lib/python3/dist-packages/lava_dispatcher/job.py (and can see in job output that dispatcher tmp directory isn't cleaned anymore) but somehow the directory still disappears, so I don't know how to debug this further.
So what's going wrong here? How to get the overlay working?
Running LAVA 2023.01 on Debian 11.6, full log see attached.
Thanks in advance!
Hi Everyone,
My board has multiple uarts and they are designed to act as different
serial consoles of platform OS. So I am trying to set the desired
connection (serial) while calling the respective platform boot/flash
method from the job description. Means i need to utilise the same board and
have to call suitable serial console from connection list to get boot
logs.
{% set UART_PORTS = {"SE-UART": "AB0KOQF7", "UART2": "A10LOBA4", "UART4":
"AB0LPSO7"} %}
{% set connection_list = ['uart2', 'uart4'] %}
{% set connection_tags = {'uart2': ['primary','telnet'], 'uart4':
['telnet']} %}
{% set connection_commands = {'uart2': 'telnet 10.10.4.140 4004', 'uart4':
'telnet 10.10.4.140 4002'} %}
How to set required serial(uart2 or uart4) from connection list in job
description??
Regards
Nagendra S
Hi Team,
Facing an issue while unpack the overlay in some custom location other than "/" directory. From the LAVA linaro documentation I came to know that the -C / command to tar is essential or the test shell will not be able to start. Below are the issues that I am facing because of this.
* My / directory is a read only one and I want it in some /etc or /var.
* The LAVA job is getting stuck while doing the unpack with the command below in job definition.
transfer_overlay:
download_command: cd /tmp; wget
unpack_command: tar -C /tmp -xzf
Below I am attaching the test log from LAVA.
[cid:image001.png@01D9455A.1AD8F6A0]
How we can solve the read only filesystem image issue for unpacking the overlay other than "/" directory ?
Regards,
Sarath P T
Hey there,
I set up LAVA, and ran some jobs (e.g qemu from tutorial) which went fine - but I noticed HTTP 500 status code on /api/help page. Which wasn't severe as I thought I might ask that later. But this monday I discovered that /accounts/login/ isn't working anymore, HTTP 500 status code too! Of course I didn't change anything... (everybody says that) and honestly can't say when this broke as I only logged in once after install. Django log says "django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist."and as far as I can see Sites reside in database?
As I'm new to LAVA I don't know how to debug and to solve this, can you please help me? Is there a way to re-install the sites/templates?
Logs that might be relevant are attached.
After install (and qemu setup) I noticed that /var is full. This is resolved (deleted some docker images), but might be relevant.
Running on current Debian 11 as apt install, recent LAVA version.
Thanks in advance
Stefan