-
Incident report
-
Resolution: Won't fix
-
Blocker
-
None
-
1.8.17, 2.0.8
While performing a zabbix upgrade from 1.8.17 to 2.0.8 i got the following
I analyzed the db-schemas.
(see uploaded files, created by "mysqldump --no-data -R zabbix_t")
1.) Created a fresh 1.8.17 schema (zabbix_1.8.17_fresh_install.sql)
2.) Executed the 2.0.8 migration scripts on the fresh 1.8.17 (zabbix_1.8_after_2.0.8_upgrade.sql)
3.) Created a fresh 2.0.8 schema (zabbix_2.0.8_fresh_install.sql)
As you can see in the diff, there are differences:
--- zabbix_1.8_after_2.0.8_upgrade.sql 2013-10-07 13:20:04.569343388 +0200 +++ zabbix_2.0.8_fresh_install.sql 2013-10-07 13:27:03.161351793 +0200 @@ -254,7 +254,7 @@ `ok_unack_style` int(11) NOT NULL DEFAULT '1', `ok_ack_style` int(11) NOT NULL DEFAULT '1', `snmptrap_logging` int(11) NOT NULL DEFAULT '1', - `server_check_interval` int(11) NOT NULL DEFAULT '60', + `server_check_interval` int(11) NOT NULL DEFAULT '10', PRIMARY KEY (`configid`), KEY `c_config_1` (`alert_usrgrpid`), KEY `c_config_2` (`discovery_groupid`), @@ -2399,4 +2399,4 @@ /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; /*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */; --- Dump completed on 2013-10-07 13:05:54 +-- Dump completed on 2013-10-07 13:09:08