Hi,
What is the procedure to follow in order to upgrade LAVA to a new release while preserving the test results database? I am using the docker-based setup.
I tried
sudo tar cvzf lava-server-pgdata-backup.tgz /var/lib/docker/volumes/lava-server-pgdata <wipe away old LAVA, rebase to latest> sudo tar xvzf lava-server-pgdata-backup.tgz -C /var/lib/docker/volumes/lava-server-pgdata
But the old results don't seem to show up in the UI after the upgrade. Also the user accounts, settings, etc. are gone, and it'd have been nice to keep them.
Thanks, Vincent
Hello,
why do you need to drop the database? LAVA will automatically migrate the database to the new database schema (if needed).
Rgds
Le mar. 16 juin 2020 à 20:11, Vincent Wan vincent.wan@linaro.org a écrit :
Hi,
What is the procedure to follow in order to upgrade LAVA to a new release while preserving the test results database? I am using the docker-based setup.
I tried
sudo tar cvzf lava-server-pgdata-backup.tgz /var/lib/docker/volumes/lava-server-pgdata <wipe away old LAVA, rebase to latest> sudo tar xvzf lava-server-pgdata-backup.tgz -C /var/lib/docker/volumes/lava-server-pgdata
But the old results don't seem to show up in the UI after the upgrade. Also the user accounts, settings, etc. are gone, and it'd have been nice to keep them.
Thanks, Vincent
--
Vincent Wan Linaro.org _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
In our LITE docker setup (https://github.com/Linaro/lite-lava-docker-compose), when I upgrade I would typically run 'make clean' that does the following:
docker-compose rm -vsf
docker volume rm -f lava-server-pgdata lava-server-joboutputlava-server-devices lava-server-health-checks
before doing a rebase to the latest, which would point to the latest LAVA via a couple of lines in the '.env' file:
DC_SERVER_IMAGE=lavasoftware/lava-server:*2020.05* DC_DISPATCHER_IMAGE=lavasoftware/lava-dispatcher:*2020.05*
Then I would run 'docker-compose build; docker-compose up' again. The procedure works, except for the fact that I'd lose the user settings and the existing test results in the process. Are you saying I can omit the steps in 'make clean' altogether? I had thought it was necessary to remove the containers and rebuild them for an upgrade to start from a clean slate.
Thanks, Vincent
On Fri, 19 Jun 2020 at 05:16, Remi Duraffort remi.duraffort@linaro.org wrote:
Hello,
why do you need to drop the database? LAVA will automatically migrate the database to the new database schema (if needed).
Rgds
Le mar. 16 juin 2020 à 20:11, Vincent Wan vincent.wan@linaro.org a écrit :
Hi,
What is the procedure to follow in order to upgrade LAVA to a new release while preserving the test results database? I am using the docker-based setup.
I tried
sudo tar cvzf lava-server-pgdata-backup.tgz /var/lib/docker/volumes/lava-server-pgdata <wipe away old LAVA, rebase to latest> sudo tar xvzf lava-server-pgdata-backup.tgz -C /var/lib/docker/volumes/lava-server-pgdata
But the old results don't seem to show up in the UI after the upgrade. Also the user accounts, settings, etc. are gone, and it'd have been nice to keep them.
Thanks, Vincent
--
Vincent Wan Linaro.org _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
-- Rémi Duraffort LAVA Architect Linaro
Hello,
yes removing the containers is fine but do not drop the volumes or you will use the data that are stored inside (database+lava configuration).
Le ven. 19 juin 2020 à 18:21, Vincent Wan vincent.wan@linaro.org a écrit :
In our LITE docker setup ( https://github.com/Linaro/lite-lava-docker-compose), when I upgrade I would typically run 'make clean' that does the following:
docker-compose rm -vsfdocker volume rm -f lava-server-pgdata lava-server-joboutputlava-server-devices lava-server-health-checks
before doing a rebase to the latest, which would point to the latest LAVA via a couple of lines in the '.env' file:
DC_SERVER_IMAGE=lavasoftware/lava-server:*2020.05* DC_DISPATCHER_IMAGE=lavasoftware/lava-dispatcher:*2020.05*
Then I would run 'docker-compose build; docker-compose up' again. The procedure works, except for the fact that I'd lose the user settings and the existing test results in the process. Are you saying I can omit the steps in 'make clean' altogether? I had thought it was necessary to remove the containers and rebuild them for an upgrade to start from a clean slate.
Thanks, Vincent
On Fri, 19 Jun 2020 at 05:16, Remi Duraffort remi.duraffort@linaro.org wrote:
Hello,
why do you need to drop the database? LAVA will automatically migrate the database to the new database schema (if needed).
Rgds
Le mar. 16 juin 2020 à 20:11, Vincent Wan vincent.wan@linaro.org a écrit :
Hi,
What is the procedure to follow in order to upgrade LAVA to a new release while preserving the test results database? I am using the docker-based setup.
I tried
sudo tar cvzf lava-server-pgdata-backup.tgz /var/lib/docker/volumes/lava-server-pgdata <wipe away old LAVA, rebase to latest> sudo tar xvzf lava-server-pgdata-backup.tgz -C /var/lib/docker/volumes/lava-server-pgdata
But the old results don't seem to show up in the UI after the upgrade. Also the user accounts, settings, etc. are gone, and it'd have been nice to keep them.
Thanks, Vincent
--
Vincent Wan Linaro.org _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
-- Rémi Duraffort LAVA Architect Linaro
--
Vincent Wan Linaro.org
lava-users@lists.lavasoftware.org
-
Remi Duraffort -
Vincent Wan