Werk #8066: Fix problem where manual cmk -O or cmk -R would not activate changes for CMC
| Component | Configuration generation | ||
| Title | Fix problem where manual cmk -O or cmk -R would not activate changes for CMC | ||
| Date | Dec 1, 2014 | ||
| Level | Trivial Change | ||
| Class | Bug Fix | ||
| Compatibility | Compatible - no manual interaction needed | ||
| Checkmk versions & editions |
|
If you create a new host in WATO, then go to the command line, do a cmk -I and then cmk -O or cmk -R then your changes would not be activated. This is due the CMC Rushead Daemon. It had created a valid configuration after the last WATO operation. Check_MK used that configuration on the next reload. Now a cmk -O or cmk -R on the command line assumes that you have done changes on the command line and ignores the configuration of the Rushahead daemon.
Note: There is still the problem that a change on the command line cannot be activate with WATO. This will not be fixed. If you do something on the command line then please activate it on the command line.