lava-users May 2021

lava-users@lists.lavasoftware.org

3 participants
5 discussions

by koti

Hi, My test job .yaml does not provide any error while health-check trigger from GUI and give error while submitting the same test job from the command line . you can find the command line submission error as mentioned below. " lavamaster@lava$lavacli -i admin@validation jobs submit /tmp/test.yaml Unable to submit /tmp/target.yaml: <Fault 400: "Problem with submitted job data: expected str for dictionary value @ data['actions'][0]['boot']['parameters']['shutdown-message']">" " I have reported same type of bug for "soft-reboot" command support and provided the patch by lava-team for this soft-reboot support issue i.e " https://git.lavasoftware.org/lava/lava/-/merge_requests/1067/diffs#05da71b3… " Can someone provide the path for "shutdown-message" support also? Regards, Koti

3 years

Unable to get kernel boot messages in to lava job while using lava framework & telnet

by Nagendra Singamsetti

Hi , I am trying to automate the linux boot functionality on my custom boards using LAVA framework. Previously I have done it on Renesas board using LAVA it works fine.I got linux boot messages on lava job whereas i am not getting with customised board. *Issue: *I am using trace32 debugger to flash images onto the board (working fine). After that i am calling minimal method in pipeline job to get prompt strings/login But i am not getting the linux boot messages on the job. always stucks at the following: [common] connect-device Connecting to device using 'telnet 10.10.0.18 4000' <http://10.10.0.69/scheduler/job/789#L136>Setting prompt string to ['lava-test: # '] <http://10.10.0.69/scheduler/job/789#L137>end: 2.3 connect-device (duration 00:00:00) [common] <http://10.10.0.69/scheduler/job/789#L138>end: 2 boot-trace32-image (duration 00:00:28) [common] <http://10.10.0.69/scheduler/job/789#action_3>start: 3 minimal-boot (timeout 00:03:00) [common] <http://10.10.0.69/scheduler/job/789#action_3-1>start: 3.1 connect-device (timeout 00:03:00) [common] <http://10.10.0.69/scheduler/job/789#L141>Already connected <http://10.10.0.69/scheduler/job/789#L142>end: 3.1 connect-device (duration 00:00:00) [common] <http://10.10.0.69/scheduler/job/789#action_3-2>start: 3.2 auto-login-action (timeout 00:03:00) [common] <http://10.10.0.69/scheduler/job/789#L144>Setting prompt string to ['Booting Linux'] <http://10.10.0.69/scheduler/job/789#L145>auto-login-action: Wait for prompt ['Booting Linux'] (timeout 00:03:00) <http://10.10.0.69/scheduler/job/789#L146>Trying 10.10.0.18... <http://10.10.0.69/scheduler/job/789#L147>Connected to 10.10.0.18. <http://10.10.0.69/scheduler/job/789#L148>Escape character is '^]'. <http://10.10.0.69/scheduler/job/789#L149> <http://10.10.0.69/scheduler/job/789#L150>alif_asic01 4000 [115200 N81] <http://10.10.0.69/scheduler/job/789#L151> <http://10.10.0.69/scheduler/job/789#L152>auto-login-action timed out after 180 seconds <http://10.10.0.69/scheduler/job/789#L153>end: 3.2 auto-login-action (duration 00:03:00) [common] *Both telnet & serial server(ser2net) is configured.* *Uart cable attached with serial server: usb-Profolic_Technology_Inc._Usb-serial_Controller-ifoo-port0* i am getting boot log messages using telnet manually but not with lava. *Manual log with telnet:* $ telnet 10.10.0.18 4000 Trying 10.10.0.18... Connected to 10.10.0.18. Escape character is '^]'. alif_asic01 4000 [115200 N81] Booting Linux on physical CPU 0x0 Linux version 5.4.25-00024-g9283a6810958-dirty (nishit@alif) (gcc version 9.2.0 (GCC)) #72 Tue Apr 20 15:41:31 IST 2021 #HGG1 CPU: ARMv8-a aarch32 Processor [411fd010] revision 0 (ARMv8), cr=50c5383d CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache #HGG1.1 OF: fdt: Machine model: corstone700 [PFA] yaml job thanks Regards Nagendra S

3 years, 10 months

iso-installer for ubuntu 20.04

by Moein Shafi

Hello everyone, I'm new to LAVA and I have some issue with 'iso-installer' for ubuntu 20.04 . As you know, in ubuntu 20.04 the preseed file would not use 'debian_installer' and use 'subiquity' instead, Also LAVA does not support 'subiquity' for 'iso-installer', so I don't know how can I use 'iso-installer' for testing my ubuntu 20.04.

3 years, 10 months

Docker-compose setup broken by 2021.04

by Westermann, Oliver

Hey, By coincidence I setup a local test instance of the lava docker-compose setup. I usually use merge master regularly, so my .env file contained DC_SERVER_IMAGE=lavasoftware/lava-server:latest. When I started this up, I get > lava-publisher_1 | ModuleNotFoundError: No module named 'environ' in the logs from various containers based upon lava-server. I tested it on my production setup as well as tested fixing my revision to 2021.03.post1, which fixes this. I checked my changes to the setup and couldn't find anything that looks related, so maybe consider this a bug report? Full callstack below, best regards Oliver Westermann Full Error Log: lava-publisher_1 | Traceback (most recent call last): lava-publisher_1 | File "/usr/share/lava-server/postinst.py", line 326, in <module> lava-publisher_1 | sys.exit(main()) lava-publisher_1 | File "/usr/share/lava-server/postinst.py", line 263, in main lava-publisher_1 | config = load_configuration() lava-publisher_1 | File "/usr/share/lava-server/postinst.py", line 127, in load_configuration lava-publisher_1 | module = importlib.import_module("lava_server.settings.prod") lava-publisher_1 | File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module lava-publisher_1 | return _bootstrap._gcd_import(name[level:], package, level) lava-publisher_1 | File "<frozen importlib._bootstrap>", line 1006, in _gcd_import lava-publisher_1 | File "<frozen importlib._bootstrap>", line 983, in _find_and_load lava-publisher_1 | File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked lava-publisher_1 | File "<frozen importlib._bootstrap>", line 677, in _load_unlocked lava-publisher_1 | File "<frozen importlib._bootstrap_external>", line 728, in exec_module lava-publisher_1 | File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed lava-publisher_1 | File "/usr/lib/python3/dist-packages/lava_server/settings/prod.py", line 23, in <module> lava-publisher_1 | import environ lava-publisher_1 | ModuleNotFoundError: No module named 'environ'

3 years, 11 months

Error updating to 2021.04

by Tim Jaacks

Hello everyone, I just wanted to update to LAVA 2021.04, but encountered the following error on 'apt-get update': Reading package lists... Done E: The repository 'https://apt.lavasoftware.org/release buster Release' is no longer signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. Is this a problem on your side? I have installed the production key, and updates used to work in the past. Best regards, Tim -- Tim Jaacks SOFTWARE DEVELOPER Garz & Fricke GmbH Schlachthofstrasse 20 21079 Hamburg T: +49 40 791899-183 E: tim.jaacks(a)garz-fricke.com WE MAKE IT YOURS! Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Stefan Heczko, Matthias Fricke, Marc-Michael Braun

3 years, 11 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users May 2021