lava-users February 2022

lava-users@lists.lavasoftware.org

6 participants
9 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

2 years, 8 months

Unable to delete Lava devices

by DAS, BHARGAV

Hi Lava Users, We are facing issue while deleting/removing some devices from LAVA. After clicking the "Delete" button located in "http://<lava url>/admin/lava_scheduler_app/device/<device we want to remove>/change/<http://%3clava%20url%3e/admin/lava_scheduler_app/device/%3cdevice%20we%20want%20to%20remove%3e/change/>" the following message is observed "Proxy Error" (check the attached image for the complete message) This error is observed only in some devices. The worker of the device is offline and in maintenance state. Regards, Bhargav

2 years, 8 months

LAVA bug when trying to use case sensitive file names with flasher

by Milosz Wasilewski

Hi, I'm trying to use flashing script with one of my IMX family boards. Flashing one of the boards requires a file which name starts with SPL-. I need to pre-process some of the downloaded files so I'm using deploy-to-downloads. After that I'm using deploy-to-flasher to flash the board with NXP's uuu tool. Unfortunately copying files from deploy-to-downloads to deploy-to-flasher results in losing the uppercase characters. This is due to LAVA internally using urllib.parse.urlparse.hostname. This method always returns lowercase strings. This doesn't matter in case of http(s) URLs but makes a difference in LAVA's internal download:// URLs. To fix that, 'hostname' should be changed to 'netloc'. I sent the patch to my branch here: https://git.lavasoftware.org/mwasilew/lava/-/tree/downloads-url-case Unfortunately I'm no longer able to create a merge request (sth wrong with authentication in gitlab). Could someone with enough powers pull this patch? Best Regards, Milosz

2 years, 9 months

Re: Job is not exiting after the timeout

by P T, Sarath

Hi Team, I could able to find the root cause of the issue just giving my observation : 1. I deleted a `cancelling` job with the ID 3834 from the GUI. 2. And for the next test run its giving an error log under worker like this . 2022-02-24 01:18:57,502 ERROR [3834] -> server error: code 503 2022-02-24 01:18:57,502 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-24 01:19:16,795 INFO PING => server 2022-02-24 01:19:17,268 INFO [3834] FINISHED => server 2022-02-24 01:19:18,666 ERROR [3834] -> server error: code 404 2022-02-24 01:19:18,666 DEBUG [3834] --> {"error": "Unknown job '3834'"} 2022-02-24 01:19:36,797 INFO PING => server 2022-02-24 01:19:37,274 INFO [3834] FINISHED => server 2022-02-24 01:19:37,509 ERROR [3834] -> server error: code 503 2022-02-24 01:19:37,509 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) So can you people help me what this behaviour is for and a solution too ? Your response will be a great help for me. Regards Sarath P T From: P T, Sarath Sent: 23 February 2022 14:26 To: lava-users(a)lists.lavasoftware.org Subject: Job is not exiting after the timeout Hi Team, Facing an issue related to the LAVA job timeout. Job is not exiting even after the timeout , its continuously loading after the job completion. Below I am giving my observations: 1. A LAVA job has executed with the job id : 3959 2. And under the worker I am getting the log as shown below : 2022-02-22 23:19:09,534 DEBUG [3959] dispatch: None 2022-02-22 23:19:09,535 DEBUG [3959] env : {'purge': True, 'overrides': {'LC_ALL': 'C.UTF-8', 'LANG': 'C', 'PATH': '/usr/local/bin:/usr/local/sbin:/bin:/usr/bin:/usr/sbin:/sbin'}} 2022-02-22 23:19:09,535 DEBUG [3959] env-dut : None 2022-02-22 23:19:09,584 INFO [3959] RUNNING => server 2022-02-22 23:19:09,850 INFO [3834] FINISHED => server 2022-02-22 23:19:10,087 ERROR [3834] -> server error: code 503 2022-02-22 23:19:10,088 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-22 23:19:28,651 INFO PING => server 2022-02-22 23:19:29,142 INFO [3834] FINISHED => server 2022-02-22 23:19:29,775 ERROR [3834] -> server error: code 503 2022-02-22 23:19:29,776 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-22 23:19:48,652 INFO PING => server 2022-02-22 23:19:49,146 INFO [3834] FINISHED => server 2022-02-22 23:19:49,391 ERROR [3834] -> server error: code 503 2022-02-22 23:19:49,391 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-22 23:20:08,653 INFO PING => server 2022-02-22 23:20:09,171 INFO [3959] running -> finished 2022-02-22 23:20:09,224 INFO [3834] FINISHED => server 2022-02-22 23:20:09,525 ERROR [3834] -> server error: code 503 2022-02-22 23:20:09,525 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-22 23:20:28,654 INFO PING => server 2022-02-22 23:20:29,147 INFO [3834] FINISHED => server 2022-02-22 23:20:29,756 ERROR [3834] -> server error: code 503 2022-02-22 23:20:29,756 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) Seems after the job execution somewhere the communication between server and worker is getting interrupted. It will be a great help if you people are looking into the issue and hope you will find the solution for the same. Regards Sarath P T

2 years, 9 months

LAVA Dispatcher on Raspberry Pi OS (64 bit)

by Colin Thorbinson

Hi All, We are planning on deploying some Raspberry Pi's as LAVA dispatchers in our lab. Does LAVA fully support Raspberry Pi OS and are there any known limitations we should be aware of? Many thanks, Colin IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

2 years, 10 months

Job is not exiting after the timeout

by P T, Sarath

Hi Team, Facing an issue related to the LAVA job timeout. Job is not exiting even after the timeout , its continuously loading after the job completion. Below I am giving my observations: 1. A LAVA job has executed with the job id : 3959 2. And under the worker I am getting the log as shown below : 2022-02-22 23:19:09,534 DEBUG [3959] dispatch: None 2022-02-22 23:19:09,535 DEBUG [3959] env : {'purge': True, 'overrides': {'LC_ALL': 'C.UTF-8', 'LANG': 'C', 'PATH': '/usr/local/bin:/usr/local/sbin:/bin:/usr/bin:/usr/sbin:/sbin'}} 2022-02-22 23:19:09,535 DEBUG [3959] env-dut : None 2022-02-22 23:19:09,584 INFO [3959] RUNNING => server 2022-02-22 23:19:09,850 INFO [3834] FINISHED => server 2022-02-22 23:19:10,087 ERROR [3834] -> server error: code 503 2022-02-22 23:19:10,088 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-22 23:19:28,651 INFO PING => server 2022-02-22 23:19:29,142 INFO [3834] FINISHED => server 2022-02-22 23:19:29,775 ERROR [3834] -> server error: code 503 2022-02-22 23:19:29,776 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-22 23:19:48,652 INFO PING => server 2022-02-22 23:19:49,146 INFO [3834] FINISHED => server 2022-02-22 23:19:49,391 ERROR [3834] -> server error: code 503 2022-02-22 23:19:49,391 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-22 23:20:08,653 INFO PING => server 2022-02-22 23:20:09,171 INFO [3959] running -> finished 2022-02-22 23:20:09,224 INFO [3834] FINISHED => server 2022-02-22 23:20:09,525 ERROR [3834] -> server error: code 503 2022-02-22 23:20:09,525 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-22 23:20:28,654 INFO PING => server 2022-02-22 23:20:29,147 INFO [3834] FINISHED => server 2022-02-22 23:20:29,756 ERROR [3834] -> server error: code 503 2022-02-22 23:20:29,756 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) Seems after the job execution somewhere the communication between server and worker is getting interrupted. It will be a great help if you people are looking into the issue and hope you will find the solution for the same. Regards Sarath P T

2 years, 10 months

Lava JOB status still shows running even after job completed

by koti

Hi, My LAVA job status still shows "Running" even when the job is completed and status does not change even after 24 hours. Due to that my other Job's pending from that dispatcher targets. My dispatcher shows these errors for /var/log/lava-dispatcher/lava-worker.log i.e " https://pastebin.com/46WFtAin" Please can someone let me know a solution to fix this issue? Regards, Koti

2 years, 10 months

Flashrom

by koti

Hi Cano Pablo, If my understanding is correct, you may want to flash the images in boot action. We can flash the same using the below boot action. " actions: - deploy: timeout: minutes: 10 to: flasher images: image: url: file: <firmware path> - boot: method: bootloader bootloader: u-boot commands: - ' xxxxx' prompts: - 'xxxxx' timeout: minutes: 10 " 1. Please provide your flash script under /etc/lava-server/dispatcher-config/devices/<device.jinja2> file as mentioned below under "flasher_deploy_commands" Example: (Note: {IMAGE} is the file mentioned in Deply action i.e "url: file: <firmware path>" {% set flasher_deploy_commands = ['/1.py', 'sleep 10', '/2.py', 'sleep 10', '/flash.sh "{IMAGE}" &', 'sleep 2', 'sleep 2'] %} 2. Please mention your bootmethod and bootloader as per your requirement. Regards, Koti On Wed, 2 Feb 2022 at 05: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 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. Flashrom (Cano, Pablo) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 1 Feb 2022 23:21:42 +0000 > From: "Cano, Pablo" <Pablo.Cano(a)Resideo.com> > Subject: [Lava-users] Flashrom > To: "lava-users(a)lists.lavasoftware.org" > <lava-users(a)lists.lavasoftware.org> > Message-ID: <SN4PR22MB33174DEF13E85267D949A52B8B269(a)SN4PR22MB3317.nam > prd22.prod.outlook.com> > Content-Type: multipart/alternative; boundary="_000_SN4PR22MB33174D > EF13E85267D949A52B8B269SN4PR22MB3317namp_" > > Hi, > Someone knows how to implement flashrom in the booting action of the > device type? >

2 years, 10 months

Flashrom

by Cano, Pablo

Hi, Someone knows how to implement flashrom in the booting action of the device type?

2 years, 10 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users February 2022