I used LAVA V1 before and I want to migrate to LAVA V2 following the guide " First steps installing LAVA V2" .
I had a problem when adding pipeline workers to the master. After input the command " sudo lava-server manage workers add <HOSTNAME>", I got error "Unknown command: 'workers'" and I failed to find help by typing "lava-server -h manage".
Can anybody help me on this step?
BTW, I want to know whether multiple workers can have the same hostname ?
Thanks in advance.
The tests in https://git.linaro.org/qa/test-definitions.git in some
cases have license in the subdirectories but there's no top level
licence file covering the whole repository. Would you like a PR
submitting to cover this or do you envisage the maintainers making this
change themselves? We're hoping to use some of these and so wanted
licences to be consistent. We'd also be prepared to review licences
in future repository changes.
The licenses that I've found all seem to be GPL v2 so I assume that is
the license flavour which should be covering the whole repos.
Hi Lava users,
I just updated lava from 2016.12 to 2017.6-1. And I found my health-check
job failed(uncomplete) after the update.
Here is the result logs before:
I checked the log and think the cause for the issue is:
error_msg: constants section not present in the device config.
What I have done:
* Try to find the "constants section" with no luck.
* Looked at the logs in /var/lava-server/ and didn't find the log specific
for the reason of this.
* Asked IRC channel and ask, answered by codehelp(thanks:)). Then tried to
replace my device-type config
in /etc/lava-server/dispatcher-config/device-types with x86.jinja2 and the
error message is the same.
Any input would by much appreciated, thank you.
Hi Lava Team,
I am using Lava image on debian stretch from https://images.validation.linaro.org/production-repo stretch-backports main & in It chart/query api is working.
Then I took latest code from lava release branch https://github.com/Linaro/lava-server/commits/release to my local branch
Tag taken :- c0b431f1b56227f6b97ba0e7859bfcc3fb29b62f refs/tags/2017.7
& build it but Lava charts is not coming when I run lava server["python manage.py runserver"] using latest code from git??
Can you please share where is latest code being used in debian stretch located?
In LAVA v1, as I remember, I can use either "device" or "device_type" to
request a device for the test.
If I use "device", for example "device": "beaglebone-black03", then the
specific device, beaglebone-black03, will be used for the test.
Can I do the same thing in LAVA v2? To request a device by using device
I've got 2 jobs stuck in canceled mode which are preventing any other job from running.
I'm running lava (2017-7) in a VM and have tried rebooting the VM to
clear the issue but without success (ie the jobs still block the queue).
an extract from /var/log/lava-server/django.log
I get this 500 error when viewing the results for the job
Is there a manual way of clearing this? The health check has
notification associated with it (and set to verbose) and every time I
reboot I get an email and irc saying that it's finished!
I'm implementing the nfsroot for my devices but it seems that when
extracting my rootfs.tar.xz lava keep the parent folder rootfs and didn't
extract all the files in extract-nfsrootfs-XXXXX so that the lava test
overlay is putting outside of rootfs folder and raises an error during
Is there a way in job definition to ask lava to put the test overlay in the
rootfs folder ?
- Confidential -
hope you're fine ! I'm quite stuck in my platform development: indeed, I
succedded in adding my own device type, I'm able to boot on linux by TFTP
and to perform auto-login actions.
However, I face difficulties with test-shell.
I have the following error:
And the definition of stage is:
Stage value seems to be none and I also realized that my test shell isn't
downloaded from git during server processing. Thus I think, that stage is
empty because the test shell definition isn't in the temporary files. Am I
Even if I think I found my problem, I don't know how to solve it, may it be
due to my device-type config ?
Thanks a lot and have a nice day !
- Confidential -