[checkmk-commits] [Checkmk/checkmk] c0a461: omd update(5): umount `tmpfs` on failure

Branch: refs/heads/2.3.0 Home: https://github.com/Checkmk/checkmk Commit: c0a4619a78a0d217b8e0a40bdf5028bf1fc932d8 https://github.com/Checkmk/checkmk/commit/c0a4619a78a0d217b8e0a40bdf5028bf1… Author: Solomon Jacobs <solomon.jacobs(a)checkmk.com> Date: 2024-03-04 (Mon, 04 Mar 2024) Changed paths: M omd/packages/omd/omdlib/main.py M omd/packages/omd/omdlib/tmpfs.py M omd/packages/omd/omdlib/update.py M tests/unit/omdlib/test_update.py Log Message: ----------- omd update(5): umount `tmpfs` on failure The command `omd update` must abort, if the pre-update checks fail. Different update steps depend on each other, so reordering these steps is not trivial. Instead we make it possible to rollback changes, which have been made before the pre-update checks. An additional benefit is that if the user cancels the update (using the `abort` option or CTRL-C), then the site can be in a consistent state. Note that failures after the pre-update checks are beyond the scope of the 2.3.0. These type of failures are not covered by the rollback mechanism. `tmpfs` is unmounted if `omd update` is called. This even applies if the customer does not commit to the update. The rollback needs to umount `tmpfs` if it has been repopulated based on the new version. CMK-15866 Change-Id: I3f2be64c3a277ab57a1d3c07d803a13763757868 To unsubscribe from these emails, change your notification settings at https://github.com/Checkmk/checkmk/settings/notifications