Hi. I'm using Icinga 2.10.5 with a Master and multiple Clients. Those Clients fall into three categories: development, test and production. All run Debian Stretch.
Yesterday two of my development machines got updated to Icinga 2.11, and some (not all) of my service checks on those machines then failed with "check command does not exist". No configuration changes were made at the same time. I downgraded Icinga back to 2.10.5 but this did not fix the problem. Fortunately: a) these were "only" development machines b) we take daily backups of every entire machine c) no significant data is stored on any single Client I ended up fixing the problem by restoring the previous backup of these two machines. I have pinned Icinga at version 2.10.x for the time being on all machines so that Debian package upgrades don't take it to 2.11 again. I have read https://icinga.com/docs/icinga2/latest/doc/16-upgrading-icinga-2/ and seen quite how much has changed between 2.10 and 2.11. I rather agree with the comment in there that it could well have been called Icinga 3.0. I have three questions: 1. Is there any way to run 2.10.5 on my Master machine and update Clients to 2.11 and keep service checks running? 2. If I upgrade my Master to 2.11, will this cause problems for the Clients still running 2.10.5? 3. Once a machine has been upgraded from 2.10.5 to 2.11, if I run into problems, is there any way to downgrade back to 2.10.5 (short of restoring the backup of the whole machine)? Because my Client machines are in development, test and production clusters, I cannot upgrade all at the same time (especially if it turns out that the upgrade causes problems, such as I had with the development machines yesterday). We need to observe stable behaviour on development and test before we can proceed to upgrade the live environment. Therefore we have no choice but to run with mixed versions of Icinga for short periods of time (and this has worked well over the past 2 years). Thanks for any guidance on this. I am especially concerned about upgrading the Icinga Master machine, since obviously our entire monitoring infrastructure depends on that working, and being compatible with the Clients. Regards, Antony. -- 90% of networking problems are routing problems. 9 of the remaining 10% are routing problems in the other direction. The remaining 1% might be something else, but check the routing anyway. Please reply to the list; please *don't* CC me. _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
