Hello everyone,
There seems to be a bug in LAVA. I was on version 2022.04 and have also tried 2023.03. Both versions have the same bug.
The same configurations works in a 2018 build of LAVA on an old machine.
I am trying to connect to an always on board via ssh.
The healthcheck is failing with this error :
lava-dispatcher, installed at version: 2023.03https://10.1.52.17/scheduler/job/8857#L1start: 0 validatehttps://10.1.52.17/scheduler/job/8857#L2Start time: 2023-04-12 14:07:00.373707+00:00 (UTC)https://10.1.52.17/scheduler/job/8857#L3Traceback (most recent call last): File "/usr/lib/python3/dist-packages/lava_dispatcher/job.py", line 198, in validate self._validate() File "/usr/lib/python3/dist-packages/lava_dispatcher/job.py", line 183, in _validate self.pipeline.validate_actions() File "/usr/lib/python3/dist-packages/lava_dispatcher/action.py", line 190, in validate_actions action.validate() File "/usr/lib/python3/dist-packages/lava_dispatcher/actions/deploy/ssh.py", line 81, in validate if "serial" not in self.job.device["actions"]["deploy"]["connections"]: KeyError: 'connections' https://10.1.52.17/scheduler/job/8857#L4 validate duration: 0.00https://10.1.52.17/scheduler/job/8857#results_244238case: validate case_id: 244238 definition: lava result: fail https://10.1.52.17/results/testcase/244238https://10.1.52.17/scheduler/job/8857#L6Cleaning after the jobhttps://10.1.52.17/scheduler/job/8857#L7Root tmp directory removed at /var/lib/lava/dispatcher/tmp/8857https://10.1.52.17/scheduler/job/8857#L8LAVABug: This is probably a bug in LAVA, please report it.https://10.1.52.17/scheduler/job/8857#results_244239case: job case_id: 244239 definition: lava error_msg: 'connections' error_type: Bug result: failhttps://10.1.52.17/results/testcase/244239
The health check looks like this:
job_name: SSH check
timeouts: job: minutes: 10 action: minutes: 2 priority: medium visibility: public
actions: - deploy: timeout: # timeout for the connection attempt seconds: 30 to: ssh os: oe
- boot: timeout: minutes: 2 prompts: ['root@(.*):~#'] method: ssh connection: ssh
- test: timeout: minutes: 5 definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: smoke-tests-basic description: "Basic smoke test" run: steps: - lava-test-case linux-linaro-ubuntu-pwd --shell pwd - lava-test-case linux-linaro-ubuntu-uname --shell uname -a - lava-test-case linux-linaro-ubuntu-vmstat --shell vmstat - lava-test-case linux-linaro-ubuntu-ip --shell ip a from: inline name: smoke-tests-basic
Any ideas ? Best regards, Sebastian
Hello,
1/ ssh deploy is not really maintained as none of the maintainers are using this mode anymore. 2/ I guess the device-type template is missing some elements. Which device-type is this?
Rgds
Le mer. 4 oct. 2023 à 16:25, Sebastian Lucas gomme600@hotmail.com a écrit :
Hello everyone,
There seems to be a bug in LAVA. I was on version 2022.04 and have also tried 2023.03. Both versions have the same bug.
The same configurations works in a 2018 build of LAVA on an old machine.
I am trying to connect to an always on board via ssh.
The healthcheck is failing with this error :
lava-dispatcher, installed at version: 2023.03 https://10.1.52.17/scheduler/job/8857#L1start: 0 validate https://10.1.52.17/scheduler/job/8857#L2Start time: 2023-04-12 14:07:00.373707+00:00 (UTC) https://10.1.52.17/scheduler/job/8857#L3Traceback (most recent call last): File "/usr/lib/python3/dist-packages/lava_dispatcher/job.py", line 198, in validate self._validate() File "/usr/lib/python3/dist-packages/lava_dispatcher/job.py", line 183, in _validate self.pipeline.validate_actions() File "/usr/lib/python3/dist-packages/lava_dispatcher/action.py", line 190, in validate_actions action.validate() File "/usr/lib/python3/dist-packages/lava_dispatcher/actions/deploy/ssh.py", line 81, in validate if "serial" not in self.job.device["actions"]["deploy"]["connections"]: KeyError: 'connections' https://10.1.52.17/scheduler/job/8857#L4validate duration: 0.00 https://10.1.52.17/scheduler/job/8857#results_244238case: validate case_id: 244238 definition: lava result: fail https://10.1.52.17/results/testcase/244238 https://10.1.52.17/scheduler/job/8857#L6Cleaning after the job https://10.1.52.17/scheduler/job/8857#L7Root tmp directory removed at /var/lib/lava/dispatcher/tmp/8857 https://10.1.52.17/scheduler/job/8857#L8LAVABug: This is probably a bug in LAVA, please report it. https://10.1.52.17/scheduler/job/8857#results_244239case: job case_id: 244239 definition: lava error_msg: 'connections' error_type: Bug result: fail https://10.1.52.17/results/testcase/244239
The health check looks like this:
job_name: SSH check
timeouts: job: minutes: 10 action: minutes: 2 priority: medium visibility: public
actions:
deploy: timeout: # timeout for the connection attempt seconds: 30 to: ssh os: oe
boot: timeout: minutes: 2 prompts: ['root@(.*):~#'] method: ssh connection: ssh
test: timeout: minutes: 5 definitions:
- repository: metadata: format: Lava-Test Test Definition 1.0 name: smoke-tests-basic description: "Basic smoke test" run: steps: - lava-test-case linux-linaro-ubuntu-pwd --shell pwd - lava-test-case linux-linaro-ubuntu-uname --shell uname -a - lava-test-case linux-linaro-ubuntu-vmstat --shell vmstat - lava-test-case linux-linaro-ubuntu-ip --shell ip a from: inline name: smoke-tests-basic
Any ideas ? Best regards, Sebastian _______________________________________________ lava-users mailing list -- lava-users@lists.lavasoftware.org To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
Hi, Sebastian Lucas, I am newer and learning the lava. Do you know how to set the ssh passwd in device or job?
lava-users@lists.lavasoftware.org