lava-users

lava-users@lists.lavasoftware.org

4 participants
907 discussions

by Larry Shen

I met this for twice during past years, I use django shell to reset the state, FYI: sudo lava-server manage shell from lava_scheduler_app.models import Device Device.objects.filter(hostname="imx8mm-evk-sh99").update(state=Device.STATE_IDLE) -----Original Message----- From: lava-users-request(a)lists.lavasoftware.org <lava-users-request(a)lists.lavasoftware.org> Sent: Tuesday, June 7, 2022 8:00 AM To: lava-users(a)lists.lavasoftware.org Subject: [EXT] Lava-users Digest, Vol 46, Issue 3 Caution: EXT Email 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. Re: [EXTERNAL] Re: Device stuck in 'Running' (Milosz Wasilewski) ---------------------------------------------------------------------- Message: 1 Date: Mon, 6 Jun 2022 13:39:08 +0100 From: Milosz Wasilewski <milosz.wasilewski(a)foundries.io> Subject: [Lava-users] Re: [EXTERNAL] Re: Device stuck in 'Running' To: "Westermann, Oliver" <Oliver.Westermann(a)cognex.com> Cc: "lava-users(a)lists.lavasoftware.org" <lava-users(a)lists.lavasoftware.org> Message-ID: <CAH1=h_QrLjTp5g+gCgVnZ1fyi+M7tnamAqEngzxjCj--H+2wAw(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" On Thu, Jun 2, 2022 at 10:36 AM Westermann, Oliver <Oliver.Westermann(a)cognex.com> wrote: > > Hey, > > > From: Milosz Wasilewski <milosz.wasilewski(a)foundries.io> > > > > On Tue, May 31, 2022 at 9:04 PM Westermann, Oliver <Oliver.Westermann(a)cognex.com> wrote: > > > > > > Hey, > > > > > > I've a device stuck in 'Running' state, but missing the usual appending of '#<123> <Job Name> [submitter]'. > > > > > > Does somebody have some tips how to set/force the device state to 'Idle' manually? > > > > I put my bet on lava-dispatcher crashing somewhere along the way. > > Please try to restart lava-dispatcher and all services around it (webserver, ser2net, etc.). > > Did so before my mail request. We're running the docker-compose setup and I've already update (to 2022.05) and restarted (and rebuild) the containers with no success. That's weird. It should fix the issue > > > Once you've done this, you can mark the device "idle" in the admin interface. This should help. > > Can you give me some guidance here? The admin interface (as well as the lava-server cli) allow me to set the health (good, bad, maintenance, retired), but not the state. My bad, you're absolutely right. The state field doesn't seem to be editable. You might need to change it in the DB. I've no idea how it got to this point. In my case when dispatcher is restarted the device status usually fixes itself. One thing to consider is deleting the offending TestJob from DB. This might help (I didn't look at the code to confirm it) > > Unrelated sidenote: > Rebuilding the docker containers failed me. > The dispatcher requires a file from schneider electric [1], which is currently not available for me. > I found the file on Remis Github [2] and fixed my Dockerfile locally, but I will try to create a Issue in the gitlab. It's MIB for APC PDU (or some other Schneider equipment). It's only required if you're using SNMP to talk to PDU with the name instead of it's ASN.1 number. Linaro's lab-scripts [1] make use of this MIB. [1] https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.linar… Best Regards, Milosz > > Best regards, Olli > > [1] > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit. > lavasoftware.org%2Flava%2Fpkg%2Fdocker-compose%2F-%2Fblob%2Fmaster%2Fd > ispatcher%2FDockerfile%23L14&data=05%7C01%7Clarry.shen%40nxp.com%7 > Ce553a3e81ed4483b0aa508da4818b237%7C686ea1d3bc2b4c6fa92cd99c5c301635%7 > C0%7C0%7C637901568148410870%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD > AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&s > data=jQS9w3MoZmp5zq6GwQHleYhWuYRUOAyIEB7mVTPVIvc%3D&reserved=0 > [2] > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith > ub.com%2Fci-box%2Fci-box-lava-worker%2Fblob%2Fmaster%2Fpowernet428.mib > &data=05%7C01%7Clarry.shen%40nxp.com%7Ce553a3e81ed4483b0aa508da481 > 8b237%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637901568148410870% > 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik > 1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=oQ%2B4ZVu7i27IA4%2BHBD3 > mzToa4nLUurFPSP4VoFyojU0%3D&reserved=0 > ------------------------------ Subject: Digest Footer _______________________________________________ Lava-users mailing list -- lava-users(a)lists.lavasoftware.org To unsubscribe send an email to lava-users-leave(a)lists.lavasoftware.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s ------------------------------ End of Lava-users Digest, Vol 46, Issue 3 *****************************************

2 years, 3 months

Device stuck in 'Running'

by Westermann, Oliver

Hey, I've a device stuck in 'Running' state, but missing the usual appending of '#<123> <Job Name> [submitter]'. It does not accept new jobs and cycling it through it's health states does not change the state. We had to reboot our systems unplanned (and uncoordinated) today, so that might be the cause of the issue, but I would like to get my device back :D Google surfaced an old, outdated FAQ in the lava sources [1], and a bug marked as solved in our version 2021.11 [2], but both didn't really don't work as expected. Does somebody have some tips how to set/force the device state to 'Idle' manually? Best regards, Olli [1] https://git.lavasoftware.org/balikm/lava/-/blob/2015.01/doc/faq.rst [2] https://git.lavasoftware.org/lava/lava/-/issues/471

2 years, 3 months

Advice on Job definition in lava:

by pawanKumar

Hello Team, Good Day to you! I'm new to the Lava Environment and need advice on writing a job definition to run a script which can perform booting, run the tests and report results. I don't need to deploy and boot. Below is the job def. I'm trying to work. Please suggest any changes I should make. device_type: x86 job_name: Execute the script timeouts: job: minutes: 20 action: minutes: 20 connection: minutes: 5 visibility: public actions: - test: timeout: minutes: 10 definitions: - repository: metadata: format: Lava-Test Test Definition name: testing description: "Sanity Test on Beaglebone" os: - Linux scope: - functional run: steps: - "cd Folder_name/" - "./test_script.sh" Thanks.

2 years, 4 months

Running a test on dispatcher

by Milosz Wasilewski

Hi, I'm trying to test HDMI output from my DUT. The HDMI-USB capture device is plugged to the dispatcher. The test is simple: it captures a frame from the video device on the dispatcher and compares it to the reference. If the difference is below threshold, the test is passed. Is there an easy way of running such a test without starting all multi-node + docker machinery? Best Regards, Milosz

2 years, 4 months

How to retrieve the prompt content with Uboot

by Roselyne MAZIERES

Hello, We are writing an interactive test for uboot. Here is the command we send: timer start && nand read \${TMPADDR} ${nand_offset} \${TMPSIZE} && timer get || run fail And below is what we get. In the traces, after the "524288 bytes read: OK", there is the timer info: 0.080. We need to be able to catch this value and we need to perform computation on it and some comparison afterwards. Do you have a solution to do that? What would you advise us to do? Thanks a lot for your help! Best regards, Roselyne Mazières [cid:image001.png@01D8390F.5506EEC0] Internal

2 years, 5 months

need fix for "shutdown-message" support

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, 5 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, 5 months

lava-wait stuck in loop with multinode protocol

by abhilash.ramineni＠nxp.com

with multinode protocol device is not able to proceed from lava-wait sometimes, even though other device has sent lava-send message

2 years, 5 months

HTTPS configuration for LAVA Server.

by K L, Shivaschandra (DI SW CAS ES EPT OPS&QA PBU)

Hi All , We had lava-server running on HTTP , we needed to migrate to HTTPS for security reasons. We have configured our lava-server for HTTPS by configuring apache2 with root and issuing SSL certificates. Post migration from HTTP to HTTPS, lava server works fine , but we are facing issues while worker tries to connect to lava server, Following is the error that we are getting in lava-worker.log ERROR -> server error: code 503 2022-03-29 19:38:15,598 DEBUG --> HTTPSConnectionPool(host='*.com', port=443): Max retries exceeded with url: /scheduler/internal/v1/workers/<worker-name> /?version=2021.10 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1123)'))) Are there any configurations that we have to do on the worker side to enable the sever - worker communication to be up and running. If there are any documentations that need to be followed to configure HTTPS , request to provide the documentation for the same. Thanks and regards Shivaschandra K L

2 years, 5 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, 6 months

← Newer
1
...
7
8
9
10
11
12
13
...
91
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users