I have submitted a MR to allow version mismatch: https://git.lavasoftware.org/lava/lava/-/merge_requests/1466

This feature is really a *must-have* for us. At our own risks of course.

Thanks for considering it!

We also have quite a few other MRs in the pipe. Some of them are few months old, even if all comments are replied.

What is the appropriate way to get them reviewed/merged? ;-)

Thanks a lot,

Philippe

From: Lava-users <lava-users-bounces@lists.lavasoftware.org> On Behalf Of Remi Duraffort
Sent: Tuesday, January 26, 2021 10:04 AM
To: Philippe Mazet (OSS) <philippe.mazet@oss.nxp.com>
Cc: lava-users@lists.lavasoftware.org <lava-users@lavasoftware.org>
Subject: Re: [Lava-users] Worker/master version mismatch

Hello Philippe,

I tried the lava-docker-worker but found it too restrictive, since we can’t customize the Docker container at all (adding some tools, cfg files, ssh keys, etc…), and was imposing usage of Docker within the job themselves (that would force us to rewrite many of our existing tests).

That's an interesting use case. Maybe something that we might want to support.

A possibility would be to specify the docker registry that you want to use instead of docker hub.

As to “automatically run the right worker version”, I might have missed something. By checking lava-docker-worker sources, I concluded the Docker would simply refuse to start if version differs versus master. But do you mean it will automatically restart with the correct version when master is upgraded?

That would be an easy fix (just adding a settings to lava_server and return depending on the setting value). But keep in mind that this might break at any release.

Rgds

-- 

Rémi Duraffort

LAVA Architect

Linaro