Lava-users September 2021

lava-users@lists.lavasoftware.org

7 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

11 months, 3 weeks

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

11 months, 3 weeks

Re: [Lava-users] Email notifications broken in LAVA 2021.08

by Westermann, Oliver

> I actually didn?t upgrade anything myself: I am using your > docker-compose solution, on a Ubuntu 18.04 host. Just as a sidenote as I noticed this as well: We also use the docker-compose setup and while I did not investigate the reasons yet, I can confirm that our mailed notifications are broken since the recent update. I didn't care to much as we check manually either way, but I can confirm from my last e-mail that the "breaking change" was simply a rebuild of the docker compose setup with the latest updates, but no host changes. - Olli

1 year, 5 months

Re: [Lava-users] Email notifications broken in LAVA 2021.08 ?

by Remi Duraffort

Hello, Le lun. 27 sept. 2021 à 17:14, Philippe Mazet (OSS) < philippe.mazet(a)oss.nxp.com> a écrit : > I actually didn’t upgrade anything myself: I am using your docker-compose > solution, on a Ubuntu 18.04 host. > > But your image in dockerhub (lavasoftware/lava-server:2021.08) upgraded to > bullseye, yes. > Have you tried creating your own derivative of the lavasoftware/lava-server:2021.08 image and installing eventlet from pypi? Rgds > > > Thanks, > > > > Philippe > > > > > > *From:* Lava-users <lava-users-bounces(a)lists.lavasoftware.org> *On Behalf > Of *Remi Duraffort > *Sent:* Monday, September 27, 2021 5:05 PM > *To:* Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> > *Cc:* lava-users(a)lists.lavasoftware.org <lava-users(a)lavasoftware.org> > *Subject:* Re: [Lava-users] Email notifications broken in LAVA 2021.08 ? > > > > Hello, > > > > > > Le jeu. 23 sept. 2021 à 13:54, Philippe Mazet (OSS) < > philippe.mazet(a)oss.nxp.com> a écrit : > > Hi All, > > > > We are hitting a bug with LAVA 2021.08: email notifications seem to be > broken. > > We believe this is due to a bug between eventlet 0.26.0 and dnspython. > > Visibly, this is fixed in eventlet 0.32.0: > https://github.com/eventlet/eventlet/issues/619 > > > > Did you face the same bug? > > > > I guess you upgraded to bullseye? Because LAVA 2021.08 hasn't changed > anything regarding it's requirements. > > > > > > Any idea about how to fix that? > > > > Depending on which debian version you are using. Either ask a DD to upload > python-eventlet 0.32 and to upload it to bullseye-backports. > > > > > > > > Thanks a lot, > > > > Philippe > > > > Trace below: > > ERROR:lava_scheduler_app:[Errno -3] Lookup timed out > > Traceback (most recent call last): > > File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line > 435, in resolve > > return _proxy.query(name, rdtype, raise_on_no_answer=raises, > > File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line > 391, in query > > return end() > > File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line > 370, in end > > raise result[1] > > File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line > 351, in step > > a = fun(*args, **kwargs) > > File "/usr/lib/python3/dist-packages/dns/resolver.py", line 1089, in > query > > return self.resolve(qname, rdtype, rdclass, tcp, source, > > File "/usr/lib/python3/dist-packages/dns/resolver.py", line 1043, in > resolve > > timeout = self._compute_timeout(start, lifetime) > > File "/usr/lib/python3/dist-packages/dns/resolver.py", line 950, in > _compute_timeout > > raise Timeout(timeout=duration) > > dns.exception.Timeout: The DNS operation timed out after 5.104917526245117 > seconds > > _______________________________________________ > Lava-users mailing list > Lava-users(a)lists.lavasoftware.org > https://lists.lavasoftware.org/mailman/listinfo/lava-users > > > > > -- > > Rémi Duraffort > > TuxArchitect > > Linaro > -- Rémi Duraffort TuxArchitect Linaro

1 year, 5 months

two boot actions in single job

by Milosz Wasilewski

Hi, I'm trying to run a job which reboots the board. The reboot is controlled with interactive shell. After issuing 'reboot' I try to run a 'boot' action with download overlay. This unfortunately fails. If there is 'transfer_overlay' lava complains there is no overlay available to download. When I remove 'transfer_overlay' lava complains there are no tests to run. I guess I need to add 'deploy' action before the second boot, but I don't know how to do it properly. The DUT should be left on it's own and not reflashed. Here is my job definition: actions: - deploy: namespace: before timeout: minutes: 10 to: flasher images: image: .... - boot: namespace: before prompts: - "root@imx8mmevk" timeout: minutes: 10 auto_login: login_prompt: 'login:' username: fio password_prompt: "Password:" password: "fio" login_commands: - sudo su - fio method: minimal transfer_overlay: download_command: cd /home ; wget unpack_command: tar -C / -xzf - test: namespace: before timeout: minutes: 5 definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: prepare-upgrade description: "OTA upgrade" os: - debian scope: - functional run: steps: ... from: inline name: prepare-upgrade path: inline/prepare-upgrade.yaml - test: namespace: before timeout: minutes: 1 interactive: - name: reboot prompts: ['root@imx8mmevk',] script: - command: reboot name: reboot - boot: namespace: after connection-namespace: before prompts: - "root@imx8mmevk" timeout: minutes: 10 auto_login: login_prompt: 'login:' username: fio password_prompt: "Password:" password: "fio" login_commands: - sudo su - fio method: minimal transfer_overlay: download_command: cd /home ; wget unpack_command: tar -C / -xzf - test: namespace: after connection-namespace: before timeout: minutes: 5 definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: verify-rollback description: "OTA upgrade" os: - debian scope: - functional run: steps: ... from: inline name: verify-rollback path: inline/verify-rollback.yaml I removed the test steps as they're not relevant. The 'before' and 'after' namespaces are required. Without namespaces LAVA will only run last boot and test sections and ignores the ones in 'before' namespace. To conclude - does anyone know how to make this job working? Either by adding a 'dummy deploy' to the 'after' namespace or by getting rid of namespaces so all tests are executed in the defined order? Best Regards, Milosz

1 year, 5 months

Kernel message during LAVA signal breaks database

by Westermann, Oliver

Hey, Yesterday a kernel message was printed during a LAVA Signal. Lava therefore got a test named '0-mytest-cutoff[', the [ being the beginning of the timestamp of a kernel message. Afterwards several web views like the result overview were broken due to some filter not being able to deal with '0-mytest-cutoff['. We fixed this by taking lava offline and doing a search&replace on the database to rename the test. It seems to be the default to have the full kernel log on the LAVA serial output. Is this an expected behaviour and is there a good way to prevent those issues? Best regards, Olli

1 year, 5 months

Email notifications broken in LAVA 2021.08 ?

by Philippe Mazet (OSS)

Hi All, We are hitting a bug with LAVA 2021.08: email notifications seem to be broken. We believe this is due to a bug between eventlet 0.26.0 and dnspython. Visibly, this is fixed in eventlet 0.32.0: https://github.com/eventlet/eventlet/issues/619 Did you face the same bug? Any idea about how to fix that? Thanks a lot, Philippe Trace below: ERROR:lava_scheduler_app:[Errno -3] Lookup timed out Traceback (most recent call last): File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line 435, in resolve return _proxy.query(name, rdtype, raise_on_no_answer=raises, File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line 391, in query return end() File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line 370, in end raise result[1] File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line 351, in step a = fun(*args, **kwargs) File "/usr/lib/python3/dist-packages/dns/resolver.py", line 1089, in query return self.resolve(qname, rdtype, rdclass, tcp, source, File "/usr/lib/python3/dist-packages/dns/resolver.py", line 1043, in resolve timeout = self._compute_timeout(start, lifetime) File "/usr/lib/python3/dist-packages/dns/resolver.py", line 950, in _compute_timeout raise Timeout(timeout=duration) dns.exception.Timeout: The DNS operation timed out after 5.104917526245117 seconds

1 year, 5 months

Using Connection timeout for expected silence time on shell

by Paweł Wieczorek

Hi Lava Users, I'm working on a LAVA test that is not very chatty (little to no output during execution). I'm looking for a way to set expected silence time in that test and break its execution in case it's exceeded. I thought Connection timeout [1] would be my solution but by setting: timeouts: connections: lava-test-shell: seconds: 5 I was unable to get any difference in the job execution. I intentionally made timeout ridiculously small to see how it would affect the job. Please let me know if using Connection timeout for this purpose is a dead end. I'm also open for any solution suggestions (wrapping test with a script that would emit checkpoints on serial?) [1] https://lava.readthedocs.io/en/latest/technical-references/job-definition/t… Thanks, Paweł Wieczorek

1 year, 6 months

Alternate Bank booting support on NXP Layerscape boards

by Sahil Malhotra

Hi, We are working on integrating NXP Layerscape boards in LAVA. On Layerscape boards, we have a mechanism of having multiple banks. This is done mainly to protect board from getting bricked if wrong images gets flashed on board. Board is set to boot from a Bank 1 by default (controlled by switches). Now you use this bank also to flash your images, but in case the images are corrupt, board will get bricked and you will need to connect JTAG to recover the board. So here concept of Alternate Bank boot comes to help. By default board boots from Bank 1, but we will not flash the images on Bank 1, instead we will flash images on Bank 2. After flashing the images, we will boot from Bank 2 with a certain command on u-boot "qixis_reset altbank". With this command, Board boots from the Bank 2 and now we can boot up kernel on board. Since in this case, we have flashed the images on Bank 2 and even if images are corrupt, Bank 2 will get bricked, but since we have set board to boot from Bank 1 by default, Board will still be usable and you can flash the correct images on Bank 2 and get that working. So this was the concept and why we are using it. Now when we try to replicate the same behavior with LAVA, we are facing some issues. When we issue command "qixis_reset altbank" on u-boot, it just prints "=>", which lava takes as a success and issue next command and then starts waiting for the "Starting Kernel", which will not happen. Infact what should happen is that, after "qixis_reset altbank" is issued, lava should wait for some time and let board boot from Bank 2 (On Bank 2 board again will boot the u-boot only). and wait for "Hit Any key to stop autoboot" and then interrupt the board. Here is job.yaml for your reference. https://git.lavasoftware.org/lava/lava/uploads/2a530894990eca6c69648e6ad637… Please help me on this, how can i achieve this way of booting the board. Thanks Sahil Malhotra

1 year, 6 months

2023

2022

2021

2020

2019

2018

2017

2016

2015

Lava-users September 2021