lava-users

lava-users@lists.lavasoftware.org

2 participants
918 discussions

Unable to upgrade lava server/workers 2020.10

by Nagendra Singamsetti

Hi Team, 1. I am trying to upgrade lava machines with the latest version 2020.10.previously it was running on 2020.08. After Upgrading with the latest 2020.10 i can see that All machines 2 workers & 1 server went offline. Unable to start services of server/worker due to *Failed to start lava-master.service: Unit lava-master.service not found.* *Failed to start lava-slave.service: Unit lava-slave.service not found.* *i have referred following page to upgrade:* https://lava.readthedocs.io/en/latest/admin/basic-tutorials/instance/instal… 2 . I would like to know how to downgrade to previous versions. I am looking for your kind response !! Regards Nagendra S

4 years, 3 months

Re: [Lava-users] [Lava-devel] Integration of a new device

by koti koti

++ Lava-users list. Regards, Koti On Fri, 4 Dec 2020 at 17:30, <lava-devel-request(a)lists.lavasoftware.org> wrote: > Send Lava-devel mailing list submissions to > lava-devel(a)lists.lavasoftware.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.lavasoftware.org/mailman/listinfo/lava-devel > or, via email, send a message with subject or body 'help' to > lava-devel-request(a)lists.lavasoftware.org > > You can reach the person managing the list at > lava-devel-owner(a)lists.lavasoftware.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Lava-devel digest..." > > > Today's Topics: > > 1. Integration of a new device (Marcel Trattner) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 4 Dec 2020 10:50:08 +0000 > From: Marcel Trattner <marcel.trattner(a)expleogroup.com> > To: "Lava-devel(a)lists.lavasoftware.org" > <Lava-devel(a)lists.lavasoftware.org> > Cc: Alexander Wyron Wachtberger > <alexander-wyron.wachtberger(a)expleogroup.com>, Vladimir Schmidt > <vladimir.schmidt(a)expleogroup.com> > Subject: [Lava-devel] Integration of a new device > Message-ID: > < > AM9PR10MB4295B7516795BD7B514C2DF7E5F10(a)AM9PR10MB4295.EURPRD10.PROD.OUTLOOK.COM > > > > Content-Type: text/plain; charset="us-ascii" > > Dear LAVA-Team, > > We have only recently started to use LAVA in a new project and we are now > at the point of integrating a new device. As I have read in the > documentation that this is the hardest part I would like to ask for some > advice where to start and what to especially look out for. > > The current state is that LAVA, as a master and one slave is running in > two Docker containers by using the example of the following Github > repository: > > https://github.com/kernelci/lava-docker > > After reading the documentary extensively and trying things out with qemu > I'd like to try and integrate the following device: > > https://www.lantronix.com/products/sa8155p-automotive-development-platform/ > > Our plan so far would be: > Since it has a Snapdragon processor, it's running Android and it is using > fastboot for flashing, we figured we could use one of the dragonboard > Device-Type templates and duplicate it for our device. But as it comes now > to configuring the device dictionary and specifying the test jobs we are > not so sure as how to proceed and we also don't want to damage the > hardware, so we would be grateful for some help. > > Here some more information: > The DUT is connected via USB and its power supply can be turned on and off > by using Python scripts (When defining the power_on and power_off commands, > should the scripts then be on the master or on the dispatcher? And what are > all the necessary parameters for the power on/off and also the values > connection_list and connection_commands?). > It is running Android with the underlying Linux configured especially for > the hardware, so we would like to avoid deploying for the beginning and > only run some simple shell tests to see if the connection stands. > A very simple health check has been set up here< > https://paste.debian.net/1175549>, maybe you could give some feedback if > that would be sufficient and how future test jobs should be altered. > > Hope to hear from you soon > > Best Regards, > > > _________________________________________________________ > > EMAIL LEGAL MENTION / DISCLAIMER > > This message contains information that may be privileged or confidential > and is the property of the Expleo Services SAS, RCS Versailles 831 178 348, > located, 3 avenue des Pr?s, 78180 Montigny Le Bretonneux - France. It is > intended only for the person to whom it is addressed. If you are not the > intended recipient, you are not authorized to read, print, retain, copy, > disseminate, distribute, or use this message or any part thereof. If you > receive this message in error, please notify the sender immediately and > delete all copies of this message. > > Ce message contient des informations qui peuvent ?tre privil?gi?es ou > confidentielles et elles sont de la propri?t? d'Expleo Services SAS, RCS > Versailles 831 178 348, situ?, 3 avenue des Pr?s, 78180 Montigny le > Bretonneux-France. Il est destin? uniquement ? la personne ? qui est > adress?. Si vous n'?tes pas le destinataire vis?, vous n'?tes pas autoris? > ? lire, imprimer, conserver, copier, diffuser, distribuer ou utiliser ce > message ou toute partie de celui-ci. Si vous recevez ce message par erreur, > veuillez en avertir imm?diatement l'exp?diteur et supprimer toutes les > copies de ce message. >

4 years, 3 months

Failed to start lava-master.service: Unit lava-master.service not found

by Nagendra Singamsetti

Hi, I am trying to upgrade the lava server and remote workers in my lab from 2020.08 to 2020.10(latest). *I have used following steps to upgrade:* $ wget https://apt.lavasoftware.org/lavasoftware.key.asc $ sudo apt-key add lavasoftware.key.asc OK sudo apt update sudo apt upgrade lava I am getting the following Error while restarting the lava-master : *root@LavaServer:/# service lava-master startFailed to start lava-master.service: Unit lava-master.service not found.* Even the remote worker side also got the same error message: *lava@alif-blr-worker02/# service lava-slave startFailed to start lava-slave.service: Unit lava-slave.service not found.* Able to start/stop lava-server-gunicorn root@LavaServer:/# service lava-server-gunicorn start On Master(lava server): following services are enabled after upgrade(2020.10) *root@LavaServer:/# systemctl list-unit-files | grep enabled |grep lavalava-coordinator.service enabled lava-publisher.service enabled lava-scheduler.service enabled lava-server-gunicorn.service enabled lava-worker.service enabled root@LavaServer:/#root@LavaServer:/#* On Worker following services are enabled after upgrade:(2020.10) *lava@alif-blr-worker02:~$ systemctl list-unit-files | grep enabled |grep lavalava-worker.service enabled * Another Worker which is not upgraded to 2020.10 :(It is running with 2020.08) *Following services are Enabled * *root@alif-blr-worker03:/# systemctl list-unit-files | grep enabled |grep lavalava-coordinator.service enabled lava-logs.service enabled lava-master.service enabled lava-publisher.service enabled lava-server-gunicorn.service enabled lava-slave.service enabled root@alif-blr-worker03:/# * *I am getting this issue with 2020.10 . I haven't seen this issue with previous version upgrades. * Kindly help me out to solve this issue!! Thanks!! Regards Nagendra S

4 years, 3 months

"lava-master.log" time stamp does not match to my LAVA "Debian" server time

by koti koti

Hi, It looks like my "lava-master.log ("/var/log/lava-server/lava-master.log)"" (even other lava logs) timestamp does not match to the lava installed server (Debain 10/Buster) time stamp. Do I need to run any command to make sure "lava server logs" timestamp sync with Lava server time stamp? output: ##################### Debian Time: ########### lavamaster@lavamaster:/var/log/lava-server$ date Tue Dec 1 17:37:59 IST 2020 lavamaster@lavamaster:/var/log/lava-server$ lava-master.log: ############# lavamaster@lavamaster:/var/log/lava-server$ tail -f lava-master.log 2020-12-01 12:02:51,507 DEBUG - qemu 2020-12-01 12:02:51,531 DEBUG lava-logs => PING(20) 2020-12-01 12:02:54,519 DEBUG lavamaster => PING(20) 2020-12-01 12:02:58,749 DEBUG raspberrypi => PING(20) 2020-12-01 12:03:11,534 INFO scheduling health checks: 2020-12-01 12:03:11,554 INFO scheduling jobs: 2020-12-01 12:03:11,556 DEBUG - qemu 2020-12-01 12:03:11,582 DEBUG lava-logs => PING(20) 2020-12-01 12:03:14,542 DEBUG lavamaster => PING(20) 2020-12-01 12:03:18,774 DEBUG raspberrypi => PING(20) 2020-12-01 12:03:31,582 INFO scheduling health checks: 2020-12-01 12:03:31,603 INFO scheduling jobs: 2020-12-01 12:03:31,605 DEBUG - qemu 2020-12-01 12:03:31,633 DEBUG lava-logs => PING(20) 2020-12-01 12:03:34,566 DEBUG lavamaster => PING(20) Regards, Koti

4 years, 3 months

How can I upgrade my Lava software to latest version (may be 2020.10)

by koti koti

Hi, Recently I have installed Lava-Master and Lava-Dispatcher using the steps mentioned below in the corresponding servers. Server: ###### 1. #sudo install lava Worker (Dispatcher) ################### 1. #sudo install lava-dispatcher But the installeve Lava software version is the old version (*2019.01-5*). Now I want to upgrade to latest (*may be 2020.10*) lava ( https://git.lavasoftware.org/lava/lava/-/tags) Please can someone let me know the steps to upgrade my lava version to the latest? Regards, Koti

4 years, 3 months

QEMU "Health-check" job still in running state on my first Remote Worker

by koti koti

Hi, Recently I have installed "LAVA-Master" on Server and "LAVA-Worker (On Remote location)" on Raspberrypi-4 (8GB). Installation steps: ############################### ############################### Server: ###### 1. #sudo install lava Worker (Raspberrypi-4) ################### 1. #sudo install lava-dispatcher Add worker to Master ############################### ############################### 1. sudo lava-server manage device-types add qemu 2. sudo lava-server manage devices add --device-type qemu --worker raspberrypi qemu-02 3. Now I am able to see "raspberrypi" worker in green colour state in the master under "LAVA--->Scheduler-->workers". Problem/issue: ############ 1. My QEMU job(Health-check) is still in running state even after 2 days (Attached the screenshot) even though it is working if my dispatcher is from the same master server. I feels something I missed here and may be extra setups to establish proper communication between "Master" and "Remote-Worker" Please can someone suggest me as what am I missing to complete my QEMU job(Health-check) while it running in "Remote-Worker" ? Regards, Koti

4 years, 3 months

Can't find serial port when test.

by cnspring2002

Dear all, I have one issue when use one qualcomn's development board: - test: definitions: - from: inline name: auto_test path: inline/auto_test.yaml repository: metadata: description: run format: Lava-Test name: run run: steps: - lava-test-case "Android_Serial_Case" --shell "./test.py" docker: image: myimage local: true timeout: minutes: 1600 The test.py is from our customer, when run it, it show the error: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/serial/serialposix.py", line 265, in open self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK) FileNotFoundError: [Errno 2] No such file or directory: '/dev/ttyUSB0' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python3.7/site-packages/serial/serialutil.py", line 240, in __init__ self.open() File "/usr/local/lib/python3.7/site-packages/serial/serialposix.py", line 268, in open raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg)) serial.serialutil.SerialException: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0' I have linked the board to pc, and can see the "/dev/ttyUSB0" in my pc, what happened here?

4 years, 3 months

What's the suggestion for application which may need fuse in docker test shell?

by Larry Shen

Hi, We have a test which may need /dev/fuse when run in docker test shell, something like next: docker run -it --cap-add SYS_ADMIN --device /dev/fuse --security-opt apparmor:unconfined hello What's the suggestion for this case? Thanks.

4 years, 3 months

Moving boot commands from definition to device for UUU boot action

by Westermann, Oliver

Hey, I would like some advice on properly cleaning up my lava jobs. Following some examples, I now have job definitions that work for me. Each job definition contains a path to all images and the full list of boot commands, which are specific to our image setup and therefore ~40 lines, examples below. I would like to separate the boot commands into the device definition as those should stay stable and we only want to test the image files in the job. I've tried to move the -boot section to both the device definitions or the device type definition, but I did not manage to get a working boot out of that setup. If you would like to know what exactly I tried or need additional debug info, let me know. I've added @larry.shen@nxp.com as to my understanding he implemented the UUU actions, so maybe he has some good advice on best practices? Looking forward for some feedback and of cause thanks for the awesome piece of software to the developers! Best regards, Olli Example: actions: - deploy: to: uuu images: boot: url: file:///network-share/imx-boot.uuu initrd: url: file:///network-share/fitImage-fsl-image-mfgtool.bin [4 more image files] - boot: method: uuu commands: # Load SPL and U-Boot - SDP: boot -f {boot} - SDPU: delay 1000 - SDPU: write -f {boot} -offset 0x57c00 - SDPU: jump # run mfgtool ramdisk - FB: ucmd setenv fastboot_buffer ${loadaddr} - FB: download -f {initrd} [ 30 more commands ]

4 years, 3 months

Re: [Lava-users] lava-docker-worker: docker OCI runtime error

by K R, ANANTHA

Hi, I had installed docker long back and therefore not remember how I installed it exactly but I think I used "apt-get install docker.io" Here is the docker version running on my system. anantha@anantha-buster:~$ docker version Client: Version: 18.09.1 API version: 1.39 Go version: go1.11.6 Git commit: 4c52b90 Built: Sun, 14 Jun 2020 22:12:29 +0200 OS/Arch: linux/amd64 Experimental: false Server: Engine: Version: 18.09.1 API version: 1.39 (minimum version 1.12) Go version: go1.11.6 Git commit: 4c52b90 Built: Sun Jun 14 20:12:29 2020 OS/Arch: linux/amd64 Experimental: false Full log: https://paste.debian.net/1170559/ Will try with a fresh docker installation as in https://staging.validation.linaro.org/static/docs/v2/docker-admin.html#prer… From: K R, ANANTHA Sent: 06 November 2020 18:08 To: 'lava-users(a)lists.lavasoftware.org' <lava-users(a)lists.lavasoftware.org> Subject: RE: lava-docker-worker: docker OCI runtime error Hi all, I removed the "-init" flag passed to docker command in the /usr/lib/python3/dist-packages/docker_worker.py. After this the worker container started and is shown to be online in lava server web interface. Is this work around ok to be used ? I'm using the lava-docker-worker on a Debian buster (10.6) machine. Thank you, Anantha From: K R, ANANTHA Sent: 04 November 2020 20:37 To: 'lava-users(a)lists.lavasoftware.org' <lava-users(a)lists.lavasoftware.org<mailto:lava-users@lists.lavasoftware.org>> Subject: lava-docker-worker: docker OCI runtime error Hi All, This is my first post in lava support community. I was trying to setup worker using lava-docker-worker. Followed steps as documented here https://git.lavasoftware.org/lava/lava/-/blob/2020.09/doc/content/admin/adv… However I'm stuck with the error from docker daemon as shown in the bellow log. anantha@anantha-buster:~$ sudo lava-docker-worker -l DEBUG --url http://<My-LAVA-server-IP<http://%3cMy-LAVA-server-IP>> 2020.10: Pulling from lavasoftware/lava-dispatcher bb79b6b2107f: Pull complete 81b92962f1c3: Pull complete e69bdb4eac16: Pull complete Digest: sha256:27b3c2a84684bb0705e300899084bcbfcad99bc1fc1fd7917d8bec5ee47d57cb Status: Downloaded newer image for lavasoftware/lava-dispatcher:2020.10 docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. ^c Need help in regard to solve the above error. Thank you, Anantha

4 years, 4 months

← Newer
1
...
19
20
21
22
23
24
25
...
92
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users