Hi, I am having a problem with using the transfer_overlays command for a
dispatcher in docker. I cannot set the dispatcher ip no matter what I try.
I have tried using the API here : "
http://10.1.51.55/api/v0.2/workers/docker_dispatcher_hostname/config/" but
I get this error when posting : ""detail": "CSRF Failed: CSRF token missing
or incorrect.", I have tried another browser already. I have also tried
creating a dispatcher.yaml file in these locations :
/etc/lava-server/dispatcher.d/lava-dispatcher ;
/etc/lava-server/dispatcher.d/ ; /etc/lava-server/dispatcher.d/lava-master.
The ip I have set is simply ignored. Could anybody help please? Thanks
Hi lava:
Some question about lava V2 2018.11+stretch:
1、 As lava running for weeks,it tasks minutes for the master to schedule jobs to the lava-slave ,and the normal time maybe 20s below.
When we restar both lava master and lava slave,it schedule job in 20s again.
Can you tell us how to solve the problem,thanks very mutch.
[cid:image001.png@01D6ED8C.7BAFA000]
2、we want to know how lava code works,can you give us some document. Sometimes we want to modify the lava steps,but we don’t know how to do.
Hi, guys,
Recently we are running android VTS test in lava docker test shell, but find all MTP cases fail.
It reports:
01-08 07:42:38 D/ModuleDefinition: Running module armeabi-v7a HalUsbGadgetV1_0HostTest
01-08 07:42:43 I/ModuleListener: [1/5] com.android.tests.usbgadget.HalUsbGadgetV1_0HostTest#testMtp FAILURE: java.lang.AssertionError: MTP not present
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at com.android.tests.usbgadget.HalUsbGadgetV1_0HostTest.testMtp(HalUsbGadgetV1_0HostTest.java:113)
I'm a little lost currently, so before I have a deep investigation, I want to know if you can share a link about this case:
com.android.tests.usbgadget.HalUsbGadgetV1_0HostTest#testMtp
I know you guys run android tests on other product always, could share a link for us to reference? Or with good luck you know what's the potential root cause for my failure?
Thanks.
Hi team,
I am Re installing my lava machines with 2020.10. But after upgrading I
have noticed that settings.conf file is missing /etc/lava-server .
Is this expected behaviour??
2. I am unable to access the lava server within the intranet with the
latest version 2020.10. To do this I used to modify settings.conf at
/etc/lava-server/settings.conf with "ALLOWED_HOSTS" to "*". But i am
getting
Bad Request (400)
Kindly help me out to solve this issue!!
thanks
Regards
Nagendra S
Hi,
It looks like the apt release is stuck to version 2019.11: https://apt.lavasoftware.org/release/dists/buster/Release
Do I miss something?
Then I tried to use the daily apt source to install a worker (deb https://apt.lavasoftware.org/daily buster main, mentioned on https://docs.lavasoftware.org/lava/installing_on_debian.html#debian-install…), but then I have a version mismatch with my master...
Sorry to insist... but this version check is really a pain for us. A warning instead would be much more convenient.
Could you please let me know how could I force install of 2020.10 for example? (I mean, a native install, not using Docker)
Thank you very much,
Philippe
Hi Stevan,
I have followed the steps mentioned in the pages provided by you i.e "
https://docs.lavasoftware.org/lava/installing_on_debian.html#lava-repositor…
"
Still my version is same i.e "2019.01-5"
You can find my complete log at https://justpaste.me/id5P .
Only the thing is that I followed below steps
1. Install Debain buster
2. Run #sudo apt install lava
3. Run #sudo apt install lava-dispatcher
4. #wget https://apt.lavasoftware.org/lavasoftware.key.asc
5. #sudo apt-key add lavasoftware.key.asc
6. #sudo apt update
appreciated any suggestions.
Regards,
Koti
>
> ------------------------------
>
> Message: 3
> Date: Fri, 27 Nov 2020 08:57:14 +0100
> From: Stevan Radakovi? <stevan.radakovic(a)linaro.org>
> To: lava-users(a)lists.lavasoftware.org
> Subject: Re: [Lava-users] How can I upgrade my Lava software to latest
> version (may be 2020.10)
> Message-ID: <6c0c9fb0-069b-142c-59d1-2ff229f37031(a)linaro.org>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> Hello,
>
> There's everything regarding releases documented here:
>
> https://docs.lavasoftware.org/lava/installing_on_debian.html#lava-repositor…
> <
> https://docs.lavasoftware.org/lava/installing_on_debian.html#lava-repositor…
> >
> You will need to add LAVA signing key prior as described here:
>
> https://docs.lavasoftware.org/lava/installing_on_debian.html#lava-archive-s…
> <
> https://docs.lavasoftware.org/lava/installing_on_debian.html#lava-archive-s…
> >
>
> Cheers,
>
>
> On 11/27/20 8:31 AM, koti koti wrote:
> > 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
> > <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
> >
> > _______________________________________________
> > Lava-users mailing list
> > Lava-users(a)lists.lavasoftware.org
> > https://lists.lavasoftware.org/mailman/listinfo/lava-users
>
> --
> Stevan Radakovi? | LAVA Engineer
> Linaro.org <www.linaro.org> ? Open source software for ARM SoCs
>
>
Hi,
Try to list the available lava versions in your distro initially using the
command "apt policy lava" and downgrade using "sudo apt install <package
version>" .
But, there may be cases in which you must resolve some dependencies to be
able to downgrade the package through.
Hope this may helps you i.e
https://www.linuxuprising.com/2019/02/how-to-downgrade-packages-to-specific…
*Note*: We have not tried this so far. AFAIK before executing these
commands, make sure you take the backup of your lava
modified/configuration files which you have changed for your
production/running setup.
Best of luck!!.
Regards,
Koti
On Thu, 10 Dec 2020 at 17:30, <lava-users-request(a)lists.lavasoftware.org>
wrote:
>
> Date: Thu, 10 Dec 2020 17:20:08 +0530
> From: Nagendra Singamsetti <nag.singam91(a)gmail.com>
> To: lava-users(a)lists.lavasoftware.org
> Subject: [Lava-users] Unable to upgrade lava server/workers 2020.10
> Message-ID:
> <
> CAFhg_WuWOCMedoDXECg+rcFdtzwPS2ei5m8Q+mpFKjhTgKqa9w(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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
>
> *****************************************
>
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
++ 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.
>
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