Hi,
I'm trialling the fastboot support in Docker introduced in LAVA v2020.02 and getting a fundamental job error about the deploy action of the job definition. I've checked against the examples from the recent Linaro Tech Day LAVA presentation but I can't see the source of the error. Could someone familiar with this new support please take a look at the job definition please? I'm thinking it must be something obvious.
Error snippet: error_msg: None of the deployment strategies accepted your deployment parameters, reasons given: overlay: "to" parameter is not "overlay" docker: 'docker' not in the device configuration deploy methods download: "to" parameter is not "download" qemu-nfs:
Full error: https://lava.genivi.org/scheduler/job/718
Job definition: https://lava.genivi.org/scheduler/job/718/definition
One possible cause I can think of is that the LAVA Worker is running 2020.02, whilst the Server is running 2019.03+stretch. My assumption is that the job definition parsing occurs in the dispatcher but maybe that is not correct? The Server will be upgraded to match the Worker of course, but we took a two step approach whilst we first looked into Android support.
Thanks for any help,
Steve
-----Original Message----- From: Lava-users lava-users-bounces@lists.lavasoftware.org On Behalf Of Stephen Lawrence Sent: 16 April 2020 20:35 To: lava-users@lists.lavasoftware.org Subject: [Lava-users] job error with new fastboot in docker support
Hi,
I'm trialling the fastboot support in Docker introduced in LAVA v2020.02 and getting a fundamental job error about the deploy action of the job definition. I've checked against the examples from the recent Linaro Tech Day LAVA presentation but I can't see the source of the error. Could someone familiar with this new support please take a look at the job definition please? I'm thinking it must be something obvious.
Error snippet: error_msg: None of the deployment strategies accepted your deployment parameters, reasons given: overlay: "to" parameter is not "overlay" docker: 'docker' not in the device configuration deploy methods download: "to" parameter is not "download" qemu-nfs:
Full error: https://lava.genivi.org/scheduler/job/718
Job definition: https://lava.genivi.org/scheduler/job/718/definition
One part of the error that stands out is: "docker: 'docker' not in the device configuration deploy methods" Is something required to enable the support for "to: fastboot/docker: image" in the dispatcher or the device description?
Does anyone have a working test job using this new feature in a public instance they could point to? A working example to compare to could be a help. I had a look through the linaro validation instance but couldn't find an example.
Regards
Steve
On Thu, Apr 16, 2020 at 07:35:23PM +0000, Stephen Lawrence wrote:
Hi,
I'm trialling the fastboot support in Docker introduced in LAVA v2020.02 and getting a fundamental job error about the deploy action of the job definition. I've checked against the examples from the recent Linaro Tech Day LAVA presentation but I can't see the source of the error. Could someone familiar with this new support please take a look at the job definition please? I'm thinking it must be something obvious.
Error snippet: error_msg: None of the deployment strategies accepted your deployment parameters, reasons given: overlay: "to" parameter is not "overlay" docker: 'docker' not in the device configuration deploy methods download: "to" parameter is not "download" qemu-nfs:
Full error: https://lava.genivi.org/scheduler/job/718
Job definition: https://lava.genivi.org/scheduler/job/718/definition
One possible cause I can think of is that the LAVA Worker is running 2020.02, whilst the Server is running 2019.03+stretch. My assumption is that the job definition parsing occurs in the dispatcher but maybe that is not correct? The Server will be upgraded to match the Worker of course, but we took a two step approach whilst we first looked into Android support.
your problem seems to be that you are missing an adb/fastboot serial number in your device configuration - that's required for a fastboot deploy, with docker or otherwise.
fastboot: "adb_serial_number" is not in the device configuration
On Fri, Apr 17, 2020 at 02:37:45PM +0000, Stephen Lawrence wrote:
-----Original Message----- From: Lava-users lava-users-bounces@lists.lavasoftware.org On Behalf Of Stephen Lawrence Sent: 16 April 2020 20:35 To: lava-users@lists.lavasoftware.org Subject: [Lava-users] job error with new fastboot in docker support
Hi,
I'm trialling the fastboot support in Docker introduced in LAVA v2020.02 and getting a fundamental job error about the deploy action of the job definition. I've checked against the examples from the recent Linaro Tech Day LAVA presentation but I can't see the source of the error. Could someone familiar with this new support please take a look at the job definition please? I'm thinking it must be something obvious.
Error snippet: error_msg: None of the deployment strategies accepted your deployment parameters, reasons given: overlay: "to" parameter is not "overlay" docker: 'docker' not in the device configuration deploy methods download: "to" parameter is not "download" qemu-nfs:
Full error: https://lava.genivi.org/scheduler/job/718
Job definition: https://lava.genivi.org/scheduler/job/718/definition
One part of the error that stands out is: "docker: 'docker' not in the device configuration deploy methods" Is something required to enable the support for "to: fastboot/docker: image" in the dispatcher or the device description?
You don't need to do anything. This `'docker' not in the device configuration deploy methods"` is actually from the docker deployment method, i.e. to deploy docker containers as if they were "devices".
See my reply to your original post.
-----Original Message----- From: Lava-users lava-users-bounces@lists.lavasoftware.org On Behalf Of Antonio Terceiro Sent: 17 April 2020 16:03 To: lava-users@lists.lavasoftware.org Subject: Re: [Lava-users] job error with new fastboot in docker support
[snip]
your problem seems to be that you are missing an adb/fastboot serial number in your device configuration - that's required for a fastboot deploy, with docker or otherwise.
fastboot: "adb_serial_number" is not in the device configuration
Thanks for taking the time to have a look Antonio. The benefit of an experienced pair of eyes.
That's true it doesn't currently have a number set so I'll fix that. Hopefully that's it.
Have a great weekend,
Steve
lava-users@lists.lavasoftware.org
-
Antonio Terceiro -
Stephen Lawrence