Werk #14908: Activation no longer skips changes from remote sites
| Component | Setup | ||||
| Title | Activation no longer skips changes from remote sites | ||||
| Date | Sep 21, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
Activating changes in a distributed setup could report success and still show changes as pending afterwards.
Configuration changes recorded on a remote site are picked up by the central site once a minute and added to that site's pending changes. They keep their original timestamp, so they can end up behind changes that were already queued for the site and are in fact newer. The activation skipped those entries and left them in the list, although it reported success.
This was a display problem only: the changes are already active on the remote site, so no configuration was missing anywhere. The leftover entries disappeared with the next activation.
Technical background
An activation selects the changes to activate by timestamp, but used to remove the activated ones from the site's change list by position. Both agree only while that list is ordered by time, which carried over changes break. Selection and removal now use the same criterion.