Designate

DB Init/Sync Error Handling

Bug #1074081 reported by Kiall Mac Innes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Designate
Fix Released
High
Andrew Bogott
Designate grizzly-1

Bug Description

DB Init/Sync error handling is currently very poor. Errors are either not reported, or not visible enough right now.

See original description
Tags: database
Kiall Mac Innes (kiall)
summary: - DB Migration Error Handling
+ DB Init/Sync Error Handling
description: updated
Andrew Bogott (andrewbogott)
Changed in moniker:
assignee: nobody → Andrew Bogott (andrewbogott)
Revision history for this message
Andrew Bogott (andrewbogott) wrote :

Can you suggest particular errors you have in mind?

Revision history for this message
Andrew Bogott (andrewbogott) wrote :

For instance, with a corrupt DB I get a reasonable error:

$ moniker-manage database sync
Attempting to synchronize database
(DatabaseError) file is encrypted or is not a database u'PRAGMA table_info("migrate_version")' ()

Likewise with a busted migration script:

$ moniker-manage database init
Attempting to initialize database
You can only have one Python script per version, but you have: /opt/stack/moniker/moniker/storage/impl_sqlalchemy/migrate_repo/versions/004_broken.py and /opt/stack/moniker/moniker/storage/impl_sqlalchemy/migrate_repo/versions/004_changed_managed_cols_for_records.py

Kiall Mac Innes (kiall)
Changed in designate:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.