Add note about workaround for broken custom vars

refs #6572

diff --git a/doc/16-upgrading-icinga-2.md b/doc/16-upgrading-icinga-2.md
index 870b09d6903c663d89e628fe69876bdee566fa48..af6d6b9ec74f4beebdcfb8c5c17de3bda82361ee 100644 (file)
--- a/doc/16-upgrading-icinga-2.md
+++ b/doc/16-upgrading-icinga-2.md
@@ -97,6 +97,22 @@ With the removal of RHEL 5 as supported platform, we can finally use real unique
 This is reflected in generating names for e.g. API stage names. Previously it was a handcrafted
 mix of local FQDN, timestamps and random numbers.
 
+### Custom Vars not updating <a id="upgrading-to-2-9-custom-vars-not-updating"></a>
+
+A rare issue preventing the custom vars of objects created prior to 2.9.0 being updated when changed may occur. To
+remedy this the config checksums of the affected type need to be reset to trigger a full update. The following is an
+example of how to do this for Hosts in mysql:
+
+```
+$ mysql -uroot -picinga icinga
+MariaDB [icinga]> UPDATE icinga_hosts SET config_hash = NULL;
+MariaDB [icinga]> exit
+Bye
+$ sudo systemctl restart icinga2
+```
+
+Custom vars should now be up to date.
+
 
 ## Upgrading to v2.8.2 <a id="upgrading-to-2-8-2"></a>