On to, 04 touko 2023, Sebastiano Pomata wrote:
El 04/05/2023 a las 7:59, Alexander Bokovoy escribió:
>FreeIPA container is supposed to run upgrade on the data volume when you
>do upgrade images. This is one of scenarios tested by the upstream CI.
>This is documented in the upstream documentation:
>https://github.com/freeipa/freeipa-container/blob/master/README#L183-L189
>----------------------
>If you have existing container with data volume, it should be safe to
>shut it down and run new one based on newer image, with the same data
>directory bind-mounted to /data. The container logic will detect that it
>is running with data produced by different image and attempt to upgrade
>the configuration and data. Of course, keeping backup of the data
>directory for cases when the upgrade process fails is recommended.
>----------------------
>
>What probably would be good to do is to simulate incremental version
>upgrades here -- if you are going up from Fedora 36, step up to Fedora
>36:latest first, then Fedora 37:latest, then Fedora 38:latest.
>
>
I indeed already tried an upgrade of a minor version on the same base
distro and it worked fine, so probably I can give it a go at jumping
the base distro version as well, following the path you suggested.
This github action in upstream tests upgrade scenarios:
https://github.com/freeipa/freeipa-container/blob/master/.github/workflow...
There is one specifically for fedora-36 to fedora 38.
Latest run is succeeding:
https://github.com/freeipa/freeipa-container/actions/runs/4868306151/jobs...
You can look at the logs in 'Run master and replica' section on to what
to expect.
--
/ Alexander Bokovoy
Sr. Principal Software Engineer
Security / Identity Management Engineering
Red Hat Limited, Finland