Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
README.md: Correction / improvement to ser2net documentation
|
|
Update Device Types Link
|
|
Add a note about passing LOCAL as an option in ser2net_options to
mitigate certain serial connection issues.
Signed-off-by: Stephen Lawrence <stephen.lawrence@renesas.com>
|
|
Add missing ':' to syntax for 'ser2net_options' in boards.yaml doc.
Signed-off-by: Stephen Lawrence <stephen.lawrence@renesas.com>
|
|
|
|
For some case, we need to add custom volumes (like for
/var/lib/lxc/cache)
|
|
For some options we need to not have the space around them, like ones
needing "-%}" or coments.
Introduce raw_custom_option for such cases.
|
|
This patch permits to handle migrations when upgrading.
|
|
|
|
When backup size grows to several GB, tar operation can fail
with "no space left on device" error.
This is because of the limited size of /tmp on certain machines
This changes allows using a different folder.
This can be done by simply adding such line in Dockerfile:
ENV TMPDIR /wherever/tmp
|
|
In some case (long jobs), backup failed because some files were changed
during tar operation.
|
|
When backup size grows, we had cases where tar was filling up /tmp
This patch allows specifying a different tmp dir, used by tar
(through TMPDIR variable).
Example usage:
TMPDIR=/home/user/mytempdir ./backup.sh
|
|
Permit to use docker commands in slave
|
|
Install xnbd-server
|
|
When docker devices are needed, docker socket must be availlable in the
slave.
This is now possible via the new use_docker
|
|
The recent LAVA packages does not pull xnbd-server.
So we need to install it when use_nbd is set.
|
|
Enhance documentation
|
|
This patch enhance a bit the documentation
- On the reason of the install of nfs-kernel-server
- On how to upgrade
|
|
lava-master: patch: Add fix for visibility issue
|
|
This patch backport a LAVA patch which fix an issue with lavacli
commands.
|
|
2019.09
|