tyler.durden
/
icinga2
mirror of https://github.com/Icinga/icinga2.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #6572 from Icinga/bugfix/29X-custom-vars-upgrade 

Add note about workaround for broken custom vars
This commit is contained in:
Michael Friedrich 2018-08-24 11:25:08 +02:00 committed by GitHub
parent 7a22113f86 130a74d91c
commit 5f4eb6518f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/16-upgrading-icinga-2.md
View File

@ -134,6 +134,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>