Hello,
I am new to LAVA, I want to boot up my hardware(NET-I System)which is a x86_64 and install debian bookworm image over it and execute test cases. My h/w is connected to my LAVA server via a serial device.Below is the high level job that I am planning to use. But where should I specify the serial device information and other information?Could please share any example job and device .jija2 that I can refer regarding what all information needs to be provided for LAVA server to properly connect to H/W and also is u-boot correct for my usecase? or if there is any other suggestions :
device_type: your_device_type
job_name: debian_boot_test
timeouts:
job:
minutes: 15
action:
minutes: 5
connection:
minutes: 2
actions:
- deploy:
timeout:
minutes: 10
to: tftp
images:
rootfs:
url: <Debian Image>
- boot:
method: u-boot
commands: your_device_boot_commands
prompts:
- 'login:'
parameters:
boot_options: root=/dev/ram0
- test:
timeout:
minutes: 5
definitions:
- repository:
metadata:
format: Lava-Test Test Definition 1.0
name: debian-check-test
description: "Test to verify Debian OS"
os:
- debian
run:
steps:
- echo 'Checking if OS is Debian'
- 'if [ "$(lsb_release -is)" = "Debian" ]; then echo "OS is Debian"; else echo "OS is not Debian"; fi'
from: inline
name: debian-check-test
path: inline/debian-check-test.yaml
Hello,
I would like to change path to /mnt from below:
"lava_test_dir": "/lava-%s",
"lava_test_results_dir": "/lava-%s",
I am using an immutable image and due to which don't have permission to write, so cannot create directory eg /lava-34 due to which cannot execute test. We have partition /mnt which we can mount and run the test cases over our os. But for that to work I need to change path. I tried changing it in /usr/lib/python3/dist-packages/lava_dispatcher/deployment_data.py , but jobs fails once I change it. I have only changed the debian section as the image we are using is a debian image.
Could you please help me if there is any option to make these changes while executing job or any other file for devices.
Thanks,
Sweta
Hi ,
I am trying to setup LAVA on Single Master Worker node.
When i am trying to submit job it is running but no device is getting selected nor I am getting any output on UI. When I checked the lava-scheduler it is failing with below error:
root@debian:/etc/apache2/sites-available# systemctl status lava-scheduler
× lava-scheduler.service - LAVA scheduler
Loaded: loaded (/lib/systemd/system/lava-scheduler.service; enabled; preset: enabled)
Active: failed (Result: start-limit-hit) since Tue 2024-07-02 18:52:36 IST; 7min ago
Duration: 1.472s
Process: 10345 ExecStart=/usr/bin/lava-server manage lava-scheduler --level $LOGLEVEL --log-file $LOGFILE $EVENT_URL $IPV6 (code=exited, status=0/SUCCES>
Main PID: 10345 (code=exited, status=0/SUCCESS)
CPU: 1.431s
Jul 02 18:52:35 debian systemd[1]: lava-scheduler.service: Deactivated successfully.
Jul 02 18:52:35 debian systemd[1]: lava-scheduler.service: Consumed 1.431s CPU time.
Jul 02 18:52:36 debian systemd[1]: lava-scheduler.service: Scheduled restart job, restart counter is at 5.
Jul 02 18:52:36 debian systemd[1]: Stopped lava-scheduler.service - LAVA scheduler.
Jul 02 18:52:36 debian systemd[1]: lava-scheduler.service: Consumed 1.431s CPU time.
Jul 02 18:52:36 debian systemd[1]: lava-scheduler.service: Start request repeated too quickly.
Jul 02 18:52:36 debian systemd[1]: lava-scheduler.service: Failed with result 'start-limit-hit'.
Jul 02 18:52:36 debian systemd[1]: Failed to start lava-scheduler.service - LAVA scheduler.
root@debian:/etc/apache2/sites-available# tail -f /var/log/lava-server/lava-scheduler.log
{% extends 'qemu.jinja2' %}
^^^^^^^^^^^^^^^^^^^^^^^^^
[Previous line repeated 977 more times]
File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1494, in is_up_to_date
return self._uptodate()
^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/jinja2/loaders.py", line 212, in uptodate
return os.path.getmtime(filename) == mtime
^^^^^^^^^^^^^^^^^^^^^^^^^^
RecursionError: maximum recursion depth exceeded
Also when I am accessing /admin/lava_scheduler_app/device/ I am getting " 500 Internal Server Error
maximum recursion depth exceeded"
I have registered my worker node as debian,hostname as debian and device type is qemu. Could you please what I am missing.