See https://www.icinga.com/docs/icinga2/snapshot/doc/16-upgrading-icinga-2/
- you must update database schema (as common for 2.n -> 2.n+1 update) - you
don't need to do anything special with cert location if you use standard
icinga cli/wizards, but should update deployment tools/scripts if you use
them to provision certificates.
(Regarding cert migration: patch added to new api.conf to work around
pkg_add's behaviour of updating config files if there are no local changes).
disable unity build (upstream default) everywhere, it was previously disabled on
!amd64, but the large c++ files involved are bringing my amd64 workstation to its
knees with long hangs making X unusable for many minutes at a time
security fixes (also affecting nagios; icinga 1.x is the old nagios-derived
branch, whereas 2.x is all new) -
* Bug #13709: CVE-2016-9566: Root priviledge escalation during log file opening
* Bug #10453: Icinga Classic-UI 1.13.3 and older are vulnerable to XSS - CVE-2015-8010
notable changes -
* Classic UI: Remove attribute based authorization (cgiauth.cfg is not parsed
any more)
* IDO: Remove deprecated config options
a skeleton conversion rather than something ready-to-run, and it's less work
to write a new config using the full scope of the config language than to fix
up a migrated one.
`.gnu.linkonce.t._ZN6icinga5ValueC1EPNS_6ObjectE' referenced in section `.gnu.linkonce.r._ZN6icinga5ValueC1EPNS_6ObjectE' of lib/base/CMakeFiles/base.dir/boolean-script.cpp.o: defined in discarded section `.gnu.linkonce.t._ZN6icinga5ValueC1EPNS_6ObjectE' of lib/base/CMakeFiles/base.dir/boolean-script.cpp.o
mismatch between chrooted and non-chrooted paths (there are both CLI
scripts and a web app; both need to refer to the same paths and as well
as being complicated, the patches weren't quite working correctly,
as noticed by sebastia@).
Now you must setup a symlink "/var/www/var/www -> .." instead as
described in the new version of the pkg-readme, allowing icingaweb2 to
always use /var/www paths whether inside or outside the jail.
Note: Existing users of this package will need to create that symlink too.
