Age | Commit message (Collapse) | Author | Files | Lines |
|
We missed to add a license, fix that.
Closes: #132
|
|
Support 2020.09plus
|
|
This patch fixes the warning:
SyntaxWarning: "is" with a literal. Did you mean "=="?
|
|
Add an helper to add caps
|
|
Since 2020.09, workers does not use ZMQ anymore but use a token.
This patch permit our setup to detecte when we use LAVA 2020.09+ and retrieve it from master.
|
|
If envdir already exists, lavalab-gen.py fail
|
|
When I have added screen support, it was a hack for made M3ulcb serial console works.
But for a long time ser2net works on m3ulcb.
So lava-docker discouraged usage of screen and now it is time to remove
it.
|
|
Disable IPV6 for tftp
|
|
Fix 2020.07
|
|
If version is specified, we can generate docker images with tags set to
it.
|
|
The device-types patchs were not used since 9918419127b ("Handle the change of device-type storage").
The patch was correctly modified with path hacks, but not applied.
|
|
There is no need to listen on ipv6 inside docker.
Furtheremore, this break lava-docker on non-ipv6 machine.
|
|
Misc 09 2020
|
|
This patch adds more ZMQ documentation
|
|
For fastboot/docker, lava-dispatcher-host could be necessary
|
|
Now lava-dispatcher-host package exists, we should not remove its udev
rules.
So remove only only lava-docker rules.
|
|
For backuping we dont need a tty. Furthermore, this break AGL cron
backup.
|
|
Increase LAVA version to 2020.07
|
|
Signed-off-by: Corentin LABBE <clabbe@baylibre.com>
|
|
[Fix] Ensure proper filename of public master key
|
|
Currently, the public master key is references as $LAVA_MASTER.key in
e.g. scripts/setup.sh. If the key is named master.key it is copied to
$LAVA_MASTER.key by scripts/setup.sh. However, no nameing convention for the
public master key provided to lavalab-gen.py is documented, so the worker simply
will not start if the key is stored as e.g. master-public.key. Running into such
error scenarios could simply be prevented by copying the public master key to an
appropriatly named file in lavalab-gen.py. This is done here.
|
|
Postgres fix
|
|
Fix upper case on boards.yaml
|
|
If we use persistend_db, a restart with an image containing a backup
will re-apply the backup and so overrun current DB.
So when backup is used, apply a flag to not reuse it.
|
|
Since the LAVA DB password is set in /etc/lava-server/, we need to keep
it accross restart.
So put /etc/lava-server on a volume.
This will also permit to keep some live configuration like dispatcher
IP.
|
|
By setting pg_lava_password, the final lavaserver password will be set
to this value.
|
|
The keyword list is too long, so split it in multiline, one letter per
line.
|
|
Fixes #29
Signed-off-by: Alice Ferrazzi <alice.ferrazzi@miraclelinux.com>
|
|
healthcheck need a supported url protocol scheme to work
|
|
Job error: Unsupported url protocol scheme: healthcheck
Signed-off-by: Alice Ferrazzi <alice.ferrazzi@miraclelinux.com>
|
|
Add option to add docker build args
|
|
Make docker bind the TFTP server to the correct interface
|
|
Signed-off-by: Alice Ferrazzi <alice.ferrazzi@miraclelinux.com>
|
|
Signed-off-by: Alice Ferrazzi <alice.ferrazzi@miraclelinux.com>
|
|
Support 2020.05
|
|
device-types are now in /usr/share/lava-server/device-types/ and so
device-type-patch does not work anymore.
This patch support both location
|
|
docker need some more bind mounts.
|
|
LAVA has changed the place of DB password from instance.conf to a yaml
file.
|
|
With UDP, docker sometimes can't route UDP packets to the correct
address because the source address gets mangled [1]. This happens
indeterministically because by default the kernel uses some heuristics
to decide which interface to use. But in some rare circumstances, those
can fail and a wrong source address is used. This can be worked around
by explicitly binding to a concrete interface instead of 0.0.0.0.
[1]: https://github.com/moby/libnetwork/issues/1729
Signed-off-by: Harald Seiler <hws@denx.de>
|
|
Misc 04 2020
|
|
|
|
|
|
lava-slave: handle the case where there are no entrypoints to copy
|
|
If there are no entrypoint to copy, the COPY docker action will fail.
For fixing this issue, simply copy all files instead of just "*sh".
Since the entrypoint.d directory is not empty (got an empty file) it
will always works.
The LAVA script run only *sh files so we are still safe.
|
|
Update LAVA to 2020.02
|
|
|
|
Pr 2020.01
|
|
This patch permit to adds custom entrypoints.
|
|
This patch permit to override the LAVA version in boards.yaml
For example with 'version: 2020.01'
the Dockerfile FROM lavasoftware/lava-server:2019.09
become FROM lavasoftware/lava-server:2020.01
|
|
Improve backup handling
|