lava-users

lava-users@lists.lavasoftware.org

1 participants
942 discussions

Device node in LXC is not accessible in hacking session

by Tim Jaacks

Hey everyone, I have a problem where a physical hardware device on my worker passed through to an LXC container cannot be read from or written to when I am connected to the LXC in a hacking session via SSH. I have registered the device in my static_info: {% set static_info = [ {"board_id": "GO31472"}, ] %} LAVA starts the LXC and attaches the device to it correctly: start: 2.2 lxc-add-static (timeout 00:04:50) [remote] Adding /dev/ttyUSB16, /dev/serial/by-id/usb-GFL_M_504_G_GO31472-if00-port0, /dev/bus/usb/004/008, /dev/serial/by-path/pci-0000:00:1d.3-usb-0:1:1.0-port0 nice lxc-device -n lxc-remote-10577 add /dev/ttyUSB16 nice lxc-device -n lxc-remote-10577 add /dev/serial/by-id/usb-GFL_M_504_G_GO31472-if00-port0 nice lxc-device -n lxc-remote-10577 add /dev/bus/usb/004/008 nice lxc-device -n lxc-remote-10577 add /dev/serial/by-path/pci-0000:00:1d.3-usb-0:1:1.0-port0 end: 2.2 lxc-add-static (duration 00:00:00) [remote] When I connect to the LXC via SSH using a hacking session, the device is there, but I cannot access it: root@lxc-remote-10577:~# ls -la /dev/ttyUSB16 crw-r--r-- 1 root root 180, 0 Aug 27 11:26 /dev/ttyUSB16 root@lxc-remote-10577:~# cat /dev/ttyUSB16 cat: /dev/ttyUSB16: Operation not permitted However, when I attach to the LXC directly from the worker using "lxc-attach", I can access it: root@lxc-remote-10577:~# ls -la /dev/ttyUSB16 crw-r--r-- 1 root root 180, 0 Aug 27 11:26 /dev/ttyUSB16 root@lxc-remote-10577:~# cat /dev/ttyUSB16 ��^C root@lxc-remote-10577:/# Did anybody else encounter such a problem before? Any hints on what might be the difference between lxc-attach and the SSH connection? Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Schlachthofstrasse 20 21079 Hamburg Direct: +49 40 791 899 - 183 Fax: +49 40 791899 - 39 tim.jaacks(a)garz-fricke.com www.garz-fricke.com WE MAKE IT YOURS! Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun

6 years

Test jobs to boot the target through JLink

by dhanu msys

Hi Team, Can you please share some reference test jobs to run the tests using J-Link boot method. Thanks & Regards, Dhanunjaya. P

6 years

Creating a multinode job

by Ryan Harkin

Hi folks, I'm struggling to create a working multinode job and wondered if someone could help? Here's the sample job I've submitted to try to get a handle on how multinode works: https://validation.linaro.org/scheduler/job/1963418.1#L1745 The main problem happens when LAVA executes this command on the shell: /lava-1963419/bin/lava-test-runner /lava-1963419/1 But there is no "/lava-1963419/1" directory, so then it can't find lava-common-functions and fails like this because the path is relative to a path that doesn't exist: /lava-1963419/bin/lava-test-runner: line 18: /lava-1963419/1/../bin/lava-common-functions: No such file or directory When I run a similar definition on a single node, it uses zero for the lava sub-dir, not 1, and it works: https://validation.linaro.org/scheduler/job/1963236#L2065 I tried to work out what was running here, to see if I could debug the scripts to work out where the "1" comes from. I cloned the LAVA repo and I cannot see the script "environment", and the lava-test-runner sources lava-common-functions from line 16, not 18. So now I'm curious where LAVA gets its scripts from. Another minor point, I'm following the instructions on this link: https://docs.lavasoftware.org/lava/writing-multinode.html And there are some dead links in there, eg. https://docs.lavasoftware.org/lava/examples/test-jobs/first-multinode-job.y… https://docs.lavasoftware.org/lava/examples/test-jobs/second-multinode-job.… https://docs.lavasoftware.org/lava/examples/test-jobs/bbb-lxc-ssh-guest.yaml Thanks, Ryan.

6 years

grub boot

by Hemanth K V

Hello Lava Users, Trying to boot a target in LAVA based on base-grub device type.The LAVA version installed is 2019.11. >From the GRUB command line when I manually enter following commands for network setting ,it is getting executed successfully. grub> insmod efinet grub> net_ls_cards efinet2 20:87:56:b6:74:cd efinet1 20:87:56:f1:cf:21 efinet0 20:87:56:f1:cf:22 grub> net_add_addr test efinet0 134.86.62.99 grub> net_ls_addr test 20:87:56:f1:cf:22 134.86.62.99 But when I am sending same thing via LAVA , *net_add_addr test efinet0 134.86.62.99* [H[J[1;1Hgrub> net_add_addr test efinet0 134.86.62.99 bootloader-commands: Wait for prompt ['grub>'] (timeout 00:09:38) [1;7Hn[1;8H[1;8He[1;9H[1;9Ht[1;10H[1;10H_[1;11H[1;11Ha[1;12H[1;12Hd[1;13H[1;13Hd[1;14H[1;14H_[1;15H[1;15Ha[1;16H[1;16Hd[1;17H[1;17Hd[1;18H[1;18Hr[1;19H[1;19H [1;20H[1;20Ht[1;21H[1;21He[1;22H[1;22Hs[1;23H[1;23Ht[1;24H[1;24H [1;25H[1;25H [1;26H *error: three arguments expected.* The above error will come when we don't pass 3 parameters to net_add_addr grub> net_add_addr test efinet0 error: three arguments expected. I am getting this error even though 3 arguments are getting passed. Attached is the screen shot of the Job execution log. Thanks, Hemanth.

6 years

Re: [Lava-users] Job Failure-Infrastructure error for qemu arm64

by Remi Duraffort

Hello, I ran the same job on staging (debian buster) and it's working fine: https://staging.validation.linaro.org/scheduler/job/266192 Something wrong on your system. Difficult to know. Could you send the full logs. Rgds Le mar. 14 janv. 2020 à 07:35, dhanu msys <dhanuskd.palnati(a)gmail.com> a écrit : > Hi Remi, > > Can you please check the logs and let me know what was the changes i need > to make to run the LAVA QEMU arm based test jobs. > > Thanks & Regards, > Dhanunjaya. P > > > On Mon, Dec 23, 2019 at 5:47 PM dhanu msys <dhanuskd.palnati(a)gmail.com> > wrote: > >> Hi Remi, >> >> Can you able to check the below mentioned the Log Files & Job related >> configurations along with the Job failure logs. >> >> Thanks & Regards, >> Dhanunjaya. P >> >> >> On Thu, Nov 28, 2019 at 6:01 PM dhanu msys <dhanuskd.palnati(a)gmail.com> >> wrote: >> >>> Hi Remi, >>> >>> Here I have attached the test job definition , test summary details & >>> qemu device configuration file along with device template for qemu arm64 >>> architecture. PFA. >>> >>> Regards, >>> Dhanunjaya. P >>> >>> >>> On Tue, Nov 26, 2019 at 5:19 PM dhanu msys <dhanuskd.palnati(a)gmail.com> >>> wrote: >>> >>>> Hi Remi, >>>> >>>> Here I have attached the Host Information. >>>> >>>> root@Dhanu:~# uname -a >>>> Linux Dhanu 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) >>>> x86_64 GNU/Linux >>>> >>>> root@Dhanu:~# lsb_release -a >>>> No LSB modules are available. >>>> Distributor ID: Debian >>>> Description: Debian GNU/Linux 10 (buster) >>>> Release: 10 >>>> Codename: buster >>>> >>>> root@Dhanu:~# df -h >>>> Filesystem Size Used Avail Use% Mounted on >>>> udev 1.9G 0 1.9G 0% /dev >>>> tmpfs 383M 18M 365M 5% /run >>>> /dev/sda1 289G 23G 252G 9% / >>>> tmpfs 1.9G 375M 1.6G 20% /dev/shm >>>> tmpfs 5.0M 4.0K 5.0M 1% /run/lock >>>> tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup >>>> tmpfs 383M 5.7M 377M 2% /run/user/1000 >>>> >>>> And also I have attached the CPU Info & MemInfo related information for >>>> your reference. >>>> >>>> Regards, >>>> Dhanunjaya. P >>>> >>>> >>>> On Tue, Nov 26, 2019 at 3:17 PM Remi Duraffort < >>>> remi.duraffort(a)linaro.org> wrote: >>>> >>>>> Hi, >>>>> >>>>> >>>>> >>>>>> https://staging.validation.linaro.org/scheduler/device/staging-qemu03 >>>>>> >>>>>> >>>>>> This should work, unless your system is way too old. what host are >>>>> you using? >>>>> >>>>> >>>>> Rgds >>>>> >>>>> -- >>>>> Rémi Duraffort >>>>> LAVA Architect >>>>> Linaro >>>>> >>>> -- Rémi Duraffort LAVA Architect Linaro

6 years, 1 month

Lava dispatcher compatible question.

by David

Hello, all, Recently I heard from somebody said, lava will drop stretch support from 2020.01 release, I didn't find related information, is it true? I also want to know if I remain on stretch, but still use 2019.12 release just for slave, but maybe later just upgrade master to for example 2020.06 release on buster. Will 2019.12 slave on stretch be compatible with 2020.06(Just a example version) master on buster? Will you promise it? Best Regards, David

6 years, 1 month

Lava dispatcher compatible question.

by David

6 years, 1 month

lavacli cannot fetch big logs.

by Larry Shen

Hi, there, We have one job to do some stress test, the final log is about 270MB. We use `lavacli -i production jobs logs --raw 30686` to fetch the log, it gives me next: ``` $ time lavacli -i production jobs logs --raw 30686 /usr/lib/python3/dist-packages/lavacli/__init__.py:101: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details. config = yaml.load(f_conf.read()) Unable to call 'jobs.logs': <ProtocolError for http://larry.shen:xxx@xxx.nxp.com/RPC2: 500 ('Connection broken: IncompleteRead(0 bytes read)', IncompleteRead(0 bytes read))> real 0m39.006s user 0m0.989s sys 0m0.191s ``` I check the gunicorn log, it give me: [2020-01-08 08:11:12 +0000] [188] [CRITICAL] WORKER TIMEOUT (pid:11506) Any suggestion?

6 years, 1 month

docker dispatcher qemu mount problem since 2019.11

by Dan Rue

I tried updating my lava-docker-compose repo to the latest but hit a problem mounting the overlay filesystem in qemu as of 2019.11 (2019.10 and earlier works, 2019.11 and later do not). To reproduce, clone https://github.com/danrue/lava-docker-compose/ and run "make"; observe the qemu health-check time out. The health check job can be found at https://github.com/danrue/lava-docker-compose/blob/master/server-overlay/et… The problem seems to occur when it tries to mount the overlay filesystem for the test job. I see in the release notes that the containers moved to buster in 2019.11 - related? Raw output below. Thanks, Dan / # mkdir /lava-2 mkdir /lava-2 mount /dev/disk/by-uuid/16786250-75bd-4703-9d57-7cfa618c725e -t ext2 /lava-2 / # mount /dev/disk/by-uuid/16786250-75bd-4703-9d57-7cfa618c725e -t ext2 /lava-2 mount /dev/disk/by-uuid/16786250-75bd-4703-9d57-7cfa618c725e -t ext2 /lava-2 mount: mounting /dev/disk/by-uuid/16786250-75bd-4703-9d57-7cfa618c725e on /lava-2 failed: No such file or directory ls -la /lava-2/bin/lava-test-runner / # ls -la /lava-2/bin/lava-test-runner ls -la /lava-2/bin/lava-test-runner ls: /lava-2/bin/lava-test-runner: No such file or directory Using /lava-2 export SHELL=/bin/sh / # export SHELL=/bin/sh export SHELL=/bin/sh . /lava-2/environment / # . /lava-2/environment . /lava-2/environment /bin/sh: .: can't open '/lava-2/environment' /lava-2/bin/lava-test-runner /lava-2/0 / # /lava-2/bin/lava-test-runner /lava-2/0 Test shell timeout: 10s (minimum of the action and connection timeout) /lava-2/bin/lava-test-runner /lava-2/0 /bin/sh: /lava-2/bin/lava-test-runner: not found

6 years, 1 month

Implement new deployment method

by Ilya Fedusiv

Hi! I'm trying to implement new method to lava. As a reference I took fastboot. Now I can job with my new implemented method. I want to work with lxc container as with fastboot. But same job as for fastboot with lxc, doesn't create lxc container and miss step with image validation. Only start methods which are described in /lava_dispatcher/actions/deploy/qdl.py What I miss? Kind regards, Ilya

6 years, 1 month

← Newer
1
...
31
32
33
34
35
36
37
...
95
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users