Age | Commit message (Collapse) | Author | Files | Lines |
|
When using persistent /etc/lava-server, a device-type could be copied
without proper rights.
But the fix of rights is done during docker build and at that time,
volume are not setup, so not fixed.
So the rigths fix need to be done at run time.
|
|
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.
|
|
By setting pg_lava_password, the final lavaserver password will be set
to this value.
|
|
LAVA has changed the place of DB password from instance.conf to a yaml
file.
|
|
Pr 2020.01
|
|
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
|
|
|
|
This patch upgrade LAVA to 2019.07 via their official docker images.
Along with the change of the baseimage from our lava-xx-base to official
2019.07, some minor changes are needed:
- Activate the en_US.UTF-8 locale needed for postgresql
- chown to lavaserver all copied device-types
- Fix the start scripts for using the official entrypoints
|