]> granicus.if.org Git - icinga2/commitdiff
Docs: Add a note for upgrading to 2.7
authorMichael Friedrich <michael.friedrich@icinga.com>
Wed, 20 Sep 2017 13:33:42 +0000 (15:33 +0200)
committerMichael Friedrich <michael.friedrich@icinga.com>
Wed, 20 Sep 2017 13:47:24 +0000 (15:47 +0200)
refs #5593

doc/16-upgrading-icinga-2.md

index bc7732acba42652c2360d13294b62cc4a57810b6..bd2134e83a5e731efeeabe5cf0729f50bfa35196 100644 (file)
@@ -3,6 +3,15 @@
 Upgrading Icinga 2 is usually quite straightforward. Ordinarily the only manual steps involved
 are scheme updates for the IDO database.
 
+## Upgrading to v2.7 <a id="upgrading-to-2-7"></a>
+
+v2.7.0 provided new notification scripts and commands. Please ensure to
+update your configuration accordingly. An advisory has been published [here](https://www.icinga.com/2017/08/23/advisory-for-icinga-2-v2-7-update-and-mail-notification-scripts/).
+
+In case are having troubles with OpenSSL 1.1.0 and the
+public CA certificates, please read [this advisory](https://www.icinga.com/2017/08/30/advisory-for-ssl-problems-with-leading-zeros-on-openssl-1-1-0/)
+and check the [troubleshooting chapter](15-troubleshooting.md#troubleshooting).
+
 ## Upgrading the MySQL database <a id="upgrading-mysql-db"></a>
 
 If you're upgrading an existing Icinga 2 instance, you should check the