mirror of
https://github.com/Icinga/icingadb.git
synced 2026-02-18 18:18:00 -05:00
f49fac0798
When skipping a version for an Icinga DB upgrade, all intermediate upgrade steps must be taken. While this is already stated in the documentation, it might be overlooked. This happened for one community user, upgrading from v1.1.0 to v1.2.0, skipping the intermediate schema upgrade for v1.1.1. > https://community.icinga.com/t/icingadb-failing-exactly-5-minutes-after-start/13955 First, the necessity for all upgrades in their release order was made more prominent in the documentation, hoping that less users would ignore this when skimming the upgrade docs. However, the real change here is adding another check to the CheckSchema function, verifying that all schema upgrades between the lowest known version and the highest known version in the icingadb_schema table exists. If an intermediate schema upgrade was skipped, as in the thread above, this raises a descriptive error. |
||
|---|---|---|
| .. | ||
| 02-Installation.md.d | ||
| images | ||
| 01-About.md | ||
| 02-Installation.md | ||
| 03-Configuration.md | ||
| 04-Upgrading.md | ||
| 05-Distributed-Setups.md | ||
| 06-Migration.md | ||
| 07-Operations.md | ||
| icingadb-migration.example.yml | ||
| TRADEMARKS.md | ||