4 May
2021
4 May
'21
11:03 a.m.
Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: 7832d2a4fba3773ed25a729fc79185f59f724ffc
https://github.com/tribe29/checkmk/commit/7832d2a4fba3773ed25a729fc79185f59…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-05-04 (Tue, 04 May 2021)
Changed paths:
M cmk/gui/watolib/activate_changes.py
M tests/unit/cmk/gui/watolib/test_activate_changes.py
Log Message:
-----------
Removed unused parameter
Change-Id: I19ef509e067e6bc3197e5c0dd6bd204efeb8f48d
Commit: 8d0518fd8cf80a71440e2cc8d9e7accf321dc4f2
https://github.com/tribe29/checkmk/commit/8d0518fd8cf80a71440e2cc8d9e7accf3…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-05-04 (Tue, 04 May 2021)
Changed paths:
M cmk/gui/watolib/activate_changes.py
M cmk/gui/watolib/sites.py
M tests/unit/cmk/gui/watolib/test_activate_changes.py
M tests/unit/cmk/gui/watolib/test_config_sync.py
Log Message:
-----------
Make site config directories activation specific
* The site directories are now below
<tt>var/check_mk/site_configs/[activation_id]/[site_id]</tt>.
* Extend housekeeping job ActivationCleanupBackgroundJob to also clean
up the site_configs directories.
* When removing sites from the configuration, the cleanup using
remove_site_config_directory() is not needed anymore.
Change-Id: I2a2e78f58a94a40e54cd159f3d8c967baf6987bf
Commit: 5867ffa76410dddce6d7830398df81e0beb9f326
https://github.com/tribe29/checkmk/commit/5867ffa76410dddce6d7830398df81e0b…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-05-04 (Tue, 04 May 2021)
Changed paths:
A .werks/12828
Log Message:
-----------
12828 FIX Distributed setup: Fix parallel activations breaking remote sites
Previous 2.0.0 versions could break the Checkmk configuration on remote sites
when two users tried to activate changes for a single remote site at the same
time.
This was a race condition between both processes. While the first activation
performed the synchronization to the remote site, the second activation could
modify the files that are currently being synchronized by the first process.
This could lead to incomplete configurations on the remote site.
Since the first activation did not know anything about this inconsistency, it
tried to activate the incomplete configuration on the remote site after the
sychronization which could fail with different error messages depending on
which files were not transfered.
This issue only affected the configuration of remote sites. No configuration
was lost on the central site.
If you want to prevent this issue with previous 2.0.0 releases, you need to
ensure that you don't start two activations for a site at the same time.
Change-Id: Ifb319e9ee3507a1d7e396b0aac486af60b256b2e
Compare: https://github.com/tribe29/checkmk/compare/6654baa9319f...5867ffa76410