"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "doc/16-upgrading-icinga-2.md" between
icinga2-2.11.5.tar.gz and icinga2-2.12.0.tar.gz

About: Icinga 2 is an enterprise grade monitoring system which keeps watch over networks and any conceivable network resource.

16-upgrading-icinga-2.md  (icinga2-2.11.5):16-upgrading-icinga-2.md  (icinga2-2.12.0)
# Upgrading Icinga 2 <a id="upgrading-icinga-2"></a> # Upgrading Icinga 2 <a id="upgrading-icinga-2"></a>
Upgrading Icinga 2 is usually quite straightforward. Upgrading Icinga 2 is usually quite straightforward.
Ordinarily the only manual steps involved Ordinarily the only manual steps involved
are scheme updates for the IDO database. are scheme updates for the IDO database.
Specific version upgrades are described below. Please note that version Specific version upgrades are described below. Please note that version
updates are incremental. An upgrade from v2.6 to v2.8 requires to updates are incremental. An upgrade from v2.6 to v2.8 requires to
follow the instructions for v2.7 too. follow the instructions for v2.7 too.
## Upgrading to v2.12 <a id="upgrading-to-2-12"></a>
* CLI
* New `pki verify` CLI command for better [TLS certificate troubleshooting](
15-troubleshooting.md#troubleshooting-certificate-verification)
### Behavior changes <a id="upgrading-to-2-12-behavior-changes"></a>
The behavior of multi parent [dependencies](03-monitoring-basics.md#dependencies
) was fixed to e.g. render hosts unreachable when both router uplinks are down.
Previous behaviour:
1) parentHost1 DOWN, parentHost2 UP => childHost **not reachable**
2) parentHost1 DOWN, parentHost2 DOWN => childHost **not reachable**
New behavior:
1) parentHost1 DOWN, parentHost2 UP => childHost **reachable**
2) parentHost1 DOWN, parentHost2 DOWN => childHost **not reachable**
Please review your [Dependency](09-object-types.md#objecttype-dependency) config
uration as 1) may lead to
different results for
- `last_reachable` via REST API query
- Notifications not suppressed by faulty reachability calculation anymore
### Breaking changes <a id="upgrading-to-2-12-breaking-changes"></a>
As of v2.12 our [API](12-icinga2-api.md) URL endpoint [`/v1/actions/acknowledge-
problem`](12-icinga2-api.md#icinga2-api-actions-acknowledge-problem) refuses ack
nowledging an already acknowledged checkable by overwriting the acknowledgement.
To replace an acknowledgement you have to remove the old one before adding the n
ew one.
The deprecated parameters `--cert` and `--key` for the `pki save-cert` CLI comma
nd
have been removed from the command and documentation.
## Upgrading to v2.11 <a id="upgrading-to-2-11"></a> ## Upgrading to v2.11 <a id="upgrading-to-2-11"></a>
### Bugfixes for 2.11 <a id="upgrading-to-2-11-bugfixes"></a> ### Bugfixes for 2.11 <a id="upgrading-to-2-11-bugfixes"></a>
2.11.1 on agents/satellites fixes a problem where 2.10.x as config master would send out an unwanted config marker file, 2.11.1 on agents/satellites fixes a problem where 2.10.x as config master would send out an unwanted config marker file,
thus rendering the agent to think it is autoritative for the config, and never a ccepting any new thus rendering the agent to think it is autoritative for the config, and never a ccepting any new
config files for the zone(s). **If your config master is 2.11.x already, you are not affected by this problem.** config files for the zone(s). **If your config master is 2.11.x already, you are not affected by this problem.**
In order to fix this, upgrade to at least 2.11.1, and purge away the local confi g sync storage once, then restart. In order to fix this, upgrade to at least 2.11.1, and purge away the local confi g sync storage once, then restart.
skipping to change at line 191 skipping to change at line 224
the master. One definite requirement is that the checkable host/service the master. One definite requirement is that the checkable host/service
is put into a zone. is put into a zone.
By default, the Director puts the agent host in `zones.d/master` By default, the Director puts the agent host in `zones.d/master`
and you're good to go. If you manually manage the configuration, and you're good to go. If you manually manage the configuration,
the config compiler now throws an error with `command_endpoint` the config compiler now throws an error with `command_endpoint`
being set but no `zone` defined. being set but no `zone` defined.
The most convenient way with e.g. managing the objects in `conf.d` The most convenient way with e.g. managing the objects in `conf.d`
is to move them into the `master` zone. Please continue in the is to move them into the `master` zone. Please continue in the
[troubleshooting docs](#troubleshooting-cluster-command-endpoint-errors-agent-ho sts-command-endpoint-zone) [troubleshooting docs](15-troubleshooting.md#troubleshooting-cluster-command-end point-errors-agent-hosts-command-endpoint-zone)
for further instructions. for further instructions.
#### Config Sync <a id="upgrading-to-2-11-cluster-config-sync"></a> #### Config Sync <a id="upgrading-to-2-11-cluster-config-sync"></a>
2.11 overhauls the cluster config sync in many ways. This includes the 2.11 overhauls the cluster config sync in many ways. This includes the
following under the hood: following under the hood:
- Synced configuration files are not immediately put into production, but left i nside a stage. - Synced configuration files are not immediately put into production, but left i nside a stage.
- Unsuccessful config validation never puts the config into production, addition al logging and API states are available. - Unsuccessful config validation never puts the config into production, addition al logging and API states are available.
- Zone directories which are not configured in zones.conf, are not included anym ore on secondary master/satellites/clients. - Zone directories which are not configured in zones.conf, are not included anym ore on secondary master/satellites/clients.
 End of changes. 2 change blocks. 
1 lines changed or deleted 41 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)