[dev.icinga.com #3239] test the icinga web db upgrade scripts for 1.8

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/3239

Created by mfriedrich on 2012-10-04 12:13:15 +00:00

Assignee: mhein
Status: Resolved (closed on 2012-10-11 10:05:07 +00:00)
Target Version: 1.8
Last Update: 2012-10-11 10:05:07 +00:00 (in Redmine)

---

currently, we do have

1.7.x to 1.8.0

which might get complicated if you already got the changes from 1.7.2, but applying this script - at least this snippet will fail (in mysql_v1-7-1_to_v1-7-2.sql and mysql_v1-7-x_to_v1-8-0.sql)

INSERT INTO nsm_target
    (target_name,target_description,target_class,target_type)
VALUES (
    'icinga.cronk.admin',
    'Allow user edit and delete all cronks',
    '',
    'credential'
);

the cleaner solution would be to follow the incremential way, and propose

v1-7-2_to_v1-8-0

thoughts?

[icinga-migration]

Updated by mfrosch on 2012-10-04 12:14:31 +00:00

I support v1-7-2_to_v1-8-0

[icinga-migration]

Updated by mfriedrich on 2012-10-10 17:09:49 +00:00

from the git commits in master today, i can see

changed

• mysql
• oracle

missing

• pgsql

though, changes from 1.7.2 to 1.8.0 must be tested in deep.

[icinga-migration]

Updated by mhein on 2012-10-11 10:04:46 +00:00

• Assigned to set to mhein
• Done % changed from 0 to 100

• Created new initial files
• Test upgrade path from 1.7.2 to 1.8.0
• Test general db feeling (errors, types)
• Tested on "real" servers

Fixed.

[icinga-migration]

Updated by mhein on 2012-10-11 10:05:07 +00:00

• Status changed from New to Resolved