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
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
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
Hi, guys,
When I call `results.get_testcase_results_yaml`, there is a small probability that I will get the error:
Post https://xiaotian:***@lava.sw.nxp.com/RPC2: EOF
What does "EOF" here mean, what could be the possible root cause? Thanks.
Hi, guys,
In lava, if we define e.g. "imx8mm-evk-sh01.jinja2" device dict, and run a job on this device, if possible we could get the name (imx8mm-evk-sh01) of this device directly in test shell?
I don't want to define environment again and again in jinja2 file something like "{% set environment = {'DEVICE_NAME': " imx8mm-evk-sh01"} %}"..., there possible fault & mismatch when define this.
Thanks.
