"Fossies" - the Fresh Open Source Software Archive 
"Fossies" - the Fresh Open Source Software Archive 
2.11.3_vs_2.11.4.
Specific version upgrades are described below. Please note that upgrades are incremental. An upgrade from v2.6 to v2.8 requires to follow the instructions for v2.7 too.
General
Database Schema
v2.11.0.sql upgrade script depending
on your database vendor. As of version 2.11.4, upgrade
scripts can be found at
/usr/share/icingaweb2/schema/*-upgrades/. Older versions
install these files to
/usr/share/doc/icingaweb2/schema/*-upgrades/ for RPM-based
systems and /usr/share/icingaweb2/etc/schema/*-upgrades/
for Debian or Ubuntu.Breaking changes
user:local_name macro in restrictions has been
removed. Use user.local_name now.icingacli migrate preferences before the
upgrade, if you haven't already.Framework changes affecting third-party code
Icinga\User\Preferences\Store\IniStore: Preferences in
INI files are not supported anymore.Icinga\User\Preferences\Store\DbStore: Its methods have
been added to the PreferencesStore class.Icinga\Util\String: Use
Icinga\Util\StringHelper instead.Icinga\Util\Translator: Use
\ipl\I18n\StaticTranslator::$instance or
\ipl\I18n\Translation instead.Icinga\Module\Migrate\Clicommands\DashboardCommand:
Deleted without substitution.Icinga\Web\Hook\TicketHook: Use
Icinga\Application\Hook\TicketHook instead.Icinga\Web\Hook\GrapherHook: Use
Icinga\Application\Hook\GrapherHook instead.Icinga\Module\Monitoring\Environment: Not in use.Icinga\Module\Monitoring\Backend: Use
Icinga\Module\Monitoring\Backend\MonitoringBackend
instead.loader.js.addUrlFlag(): Use
Icinga.Utils.addUrlFlag() instead.Url::setBaseUrl(): Please create a new url from scratch
instead.Url::getBaseUrl(): Use either
Url::getBasePath() or Url::getAbsoluteUrl()
now.ApplicationBootstrap::setupZendAutoloader(): Since it
does nothing, all usages removed.ApplicationBootstrap::listLocales(): Use
\ipl\I18n\GettextTranslator::listLocales() instead.Module::registerHook(): Use provideHook()
instead.Web::getMenu(): Instantiate the menu class
new Menu() directly instead.AesCrypt::encryptToBase64(): Use
AesCrypt::encrypt() instead as it also returns a base64
encoded string.AesCrypt::decryptFromBase64(): Use
AesCrypt::decrypt() instead as it also returns a base64
decoded string.InlinePie::disableNoScript(): Empty method.SimpleQuery::paginate(): Use
Icinga\Web\Controller::setupPaginationControl() and/or
Icinga\Web\Widget\Paginator instead.LdapConnection::connect(): The connection is
established lazily since .. a long time.MonitoredObject::matches(): Use
$filter->matches($object) instead.MonitoredObject::fromParams(): Deleted without
substitution.DataView::fromRequest(): Use
$backend->select()->from($viewName) instead.DataView::sort(): Use DataView::order()
instead.MonitoringBackend::createBackend(): Use
MonitoringBackend::instance() instead.DbConnection::getConnection(): Use
Connection::getDbAdapter() instead.DbQuery::renderFilter(): Use
DbConnection::renderFilter() instead.DbQuery::whereToSql(): Use
DbConnection::renderFilter() instead.General
Deprecations
dompdf
library will be dropped with version 2.12. It is highly recommended to
use Icinga PDF
Export instead.Discontinued package updates
icinga.com provides an overview about currently supported distributions.
Framework changes affecting third-party code
expandable-toggle-support has been removed. Use
class="collapsible" data-visible-height=0 to achieve the
same effect. (Available since v2.7.0).var() LESS mixin and the LESS function
extract-variable-default have been removed (introduced with
v2.9)Database Schema
v2.9.1.sql upgrade script depending on
your database vendor. In package installations this file can be found in
/usr/share/doc/icingaweb2/schema/*-upgrades/
(Debian/Ubuntu:
/usr/share/icingaweb2/etc/schema/*-upgrades/).Installation
General
latin1) is now applied. If you had previously
problems with special characters and umlauts and you've set this charset
already manually, no change is required. However, if your IDO resource
configuration has another charset configured than this, it is highly
recommended to clear this setting. Otherwise the default won't apply and
characters may still be shown incorrectly in the UI.Database Schema
v2.9.0.sql upgrade script depending on
your database vendor. In package installations this file can be found in
/usr/share/doc/icingaweb2/schema/*-upgrades/
(Debian/Ubuntu:
/usr/share/icingaweb2/etc/schema/*-upgrades/).Breaking changes
no-user/password-change has now been
changed to a grant user/password-change. Any user that had
no-user/password-change previously still cannot change
passwords. Though any user that didn't have this permission,
needs to be granted user/password-change now in order to
change passwords.Deprecations
user.local_name replaces the
user:local_name macro in restrictions, and the latter will
be removed with version 2.11INI is not configurable
anymore. A database is now mandatory.
migrate module and use the command
icingacli migrate preferences. If you already setup the
configuration database, it will work right away. If not, pass it the
resource you'd like to use as configuration database with
--resource=..ini files. (#3770)Framework changes affecting third-party code
jquery-migrate compatibility layer for Javascript
code working with jQuery 2.x has been removed. It has been introduced
with v2.7 when we upgraded jQuery to v3.4.1 in order to allow module
developers a seamless upgrade chance. If a module still has UI glitches
after an upgrade to v2.9, please contact the module developer.getHtmlForEvent of the
EventDetailsExtensionHook previously received the host or
service object of an event. Now the actual event object is passed to it
instead.Changes in packaging and dependencies
Valid for distributions:
After upgrading to version 2.8.0 you'll get the new
rh-php73 dependency installed. This is a drop-in
replacement for the previous rh-php71 dependency and only
requires the setup of a new fpm service and possibly some copying of
customized configurations.
php.ini or php-fpm settings you have tuned in the past need to be copied over to the new path:
From /etc/opt/rh/rh-php71/ to
/etc/opt/rh/rh-php73/.
Don't forget to also install any additional php-modules for PHP 7.3 you've had previously installed for e.g. Icinga Web 2 modules.
There's also a new service included which replaces the previous one for php-fpm:
Stop the old service:
systemctl stop rh-php71-php-fpm.service
Start the new service:
systemctl start rh-php73-php-fpm.service
You can now safely remove the previous dependency if you like:
yum remove rh-php71*
Discontinued package updates
Icinga Web 2 v2.8+ is not supported on these platforms:
Please consider an upgrade of your central Icinga system to a newer distribution release.
icinga.com provides an overview about currently supported distributions.
Framework changes affecting third-party code
view=compact is now deprecated.
showCompact should be used instead. Details are in pull
request #4164.required => true didn't cause the browser to complain if
such a checkbox wasn't checked. Browsers now do complain if so.#header, #sidebar,
#main, #footer, #col1,
#col2 and a column's controls. #sidebar and
#main are now additionally wrapped in a new container
#content-wrapper.Breaking changes
?_dev to your address bar to check
for log messages emitted by jquery-migrate. (https://github.com/jquery/jquery-migrate)
Your javascript code will still work, though jquery-migrate will notify
you if you're utilizing deprecated/removed functions. jquery-migrate
will be removed with Icinga Web v2.8 and code not adjusted accordingly
will stop working.dashboard.ini files. A CLI command exists to assist you
with this task. Enable the migrate module and run the
following on the host where these files exist:
icingacli migrate dashboard sections --verboseAttention
Icinga Web 2 v2.5 requires at least PHP 5.6.
Breaking changes
#) in INI files are no longer recognized as
comments by parse_ini_file
since PHP 7.0.User data structure. Everyone who
was logged in before the upgrade has to log out once.Changes in packaging and dependencies
Valid for distributions:
a2enmod php7
and restart apache2Discontinued package updates
Icinga Web 2 v2.5+ is not supported on these platforms:
Please consider an upgrade of your central Icinga system to a newer distribution release.
packages.icinga.com provides an overview about currently supported distributions.
Database schema
Icinga Web 2 v2.5.0 requires a schema update for the database. The database schema has been adjusted to support usernames up to 254 characters. This is necessary to support the new domain-aware authentication feature.
Continue here for MySQL and PostgreSQL.
Authorization beneath
Config has been renamed to Authentication. The
role, user backend and user group backend configuration which was
previously found beneath Authentication has been moved to
Application.group_filter. Users who changed
the configuration manually and used the option filter
instead have to change it back to group_filter.Icinga Web 2 installations from package on RHEL/CentOS 7 now
depend on php-ZendFramework which is available through the
EPEL repository.
Before, Zend was installed as Icinga Web 2 vendor library through the
package icingaweb2-vendor-zend. After upgrading, please
make sure to remove the package
icingaweb2-vendor-zend.
Icinga Web 2 version 2.0.0 requires permissions for accessing
modules. Those permissions are automatically generated for each
installed module in the format module/<moduleName>.
Administrators have to grant the module permissions to users and/or user
groups in the roles configuration for permitting access to specific
modules. In addition, restrictions provided by modules are now
configurable for each installed module too. Before, a module had to be
enabled before having the possibility to configure
restrictions.
The instances.ini configuration file provided by the monitoring module has been renamed to commandtransports.ini. The content and location of the file remains unchanged.
The location of a user's preferences has been changed from <config-dir>/preferences/<username>.ini to <config-dir>/preferences/<username>/config.ini. The content of the file remains unchanged.
The first release candidate of Icinga Web 2 introduces the following non-backward compatible changes:
The database schema has been adjusted and the tables
icingaweb_group and icingaweb_group_membership
were altered to ensure referential integrity. Please use the upgrade
script located in etc/schema/ to update your database
schema
Users who are using PostgreSQL < v9.1 are required to upgrade their environment to v9.1+ as this is the new minimum required version for utilizing PostgreSQL as database backend
The restrictions monitoring/hosts/filter and
monitoring/services/filter provided by the monitoring
module were merged together. The new restriction is called
monitoring/filter/objects and supports only a predefined
subset of filter columns. Please see the module's security related
documentation for more details.
Because Icinga Web 2 Beta 3 does not introduce any backward incompatible change you don't have to change your configuration files after upgrading to Icinga Web 2 Beta 3.
Icinga Web 2 Beta 2 introduces access control based on roles for secured actions. If you've already set up Icinga Web 2, you are required to create the file roles.ini beneath Icinga Web 2's configuration directory with the following content:
[administrators]
users = "your_user_name, another_user_name"
permissions = "*"After please log out from Icinga Web 2 and log in again for having all permissions granted.
If you delegated authentication to your web server using the
autologin backend, you have to switch to the
external authentication backend to be able to log in again.
The new name better reflects what's going on. A similar change affects
environments that opted for not storing preferences, your new backend is
none.
If you installed Icinga Web 2 from package, please check the upgrade scripts located in /usr/share/doc/icingaweb2/schema/mysql-upgrades (Debian/Ubuntu: /usr/share/icingaweb2/etc/schema/mysql-upgrades) to update your database schema. In case you installed Icinga Web 2 from source, please find the upgrade scripts in etc/schema/mysql-upgrades.
Note
If there isn't an upgrade file for your current version available, there's nothing to do.
Apply all database schema upgrade files incrementally.
# mysql -u root -p icingaweb2 < /usr/share/doc/icingaweb2/schema/mysql-upgrades/<version>.sqlExample: You are upgrading Icinga Web 2 from version
2.4.0 to 2.5.0. Look into the
upgrade directory:
$ ls /usr/share/doc/icingaweb2/schema/mysql-upgrades/
2.0.0beta3-2.0.0rc1.sql 2.5.0.sqlThe upgrade file 2.5.0.sql must be applied for the
v2.5.0 release. If there are multiple upgrade files involved, apply them
incrementally.
# mysql -u root -p icinga < /usr/share/doc/icingaweb2/schema/mysql-upgrades/2.5.0.sqlIf you installed Icinga Web 2 from package, please check the upgrade scripts located in /usr/share/doc/icingaweb2/schema/pgsql-upgrades (Debian/Ubuntu: /usr/share/icingaweb2/etc/schema/pgsql-upgrades) to update your database schema. In case you installed Icinga Web 2 from source, please find the upgrade scripts in etc/schema/pgsql-upgrades.
Note
If there isn't an upgrade file for your current version available, there's nothing to do.
Apply all database schema upgrade files incrementally.
# export PGPASSWORD=icingaweb2
# psql -U icingaweb2 -d icingaweb2 < /usr/share/doc/icingaweb2/schema/pgsql-upgrades/<version>.sqlExample: You are upgrading Icinga Web 2 from version
2.4.0 to 2.5.0. Look into the
upgrade directory:
$ ls /usr/share/doc/icingaweb2/schema/pgsql-upgrades/
2.0.0beta3-2.0.0rc1.sql 2.5.0.sqlThe upgrade file 2.5.0.sql must be applied for the
v2.5.0 release. If there are multiple upgrade files involved, apply them
incrementally.
# export PGPASSWORD=icingaweb2
# psql -U icingaweb2 -d icingaweb2 < /usr/share/doc/icingaweb2/schema/pgsql-upgrades/2.5.0.sql