If you try to run mg-schema-create on an existing instance it bombs out right at the beginning because it tries to create the `flights' table, which already exists.
But in the future the `flights' table might be removed in an update, which would remove this safety catch. Then running the create might partially succeed, leaving debris a production instance. Detect this situation by looking for applied schema updates, and bombing out if there are any. Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com> Acked-by: Ian Campbell <ian.campb...@citrix.com> --- mg-schema-create | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/mg-schema-create b/mg-schema-create index df5e215..e15ecb9 100755 --- a/mg-schema-create +++ b/mg-schema-create @@ -70,6 +70,13 @@ export OSSTEST_DB_USEREAL_IGNORETEST='.*' . ./cri-getconfig +updates_applied=$(./mg-schema-update list-applied) +if [ "x$updates_applied" != x ]; then + ./mg-schema-update show + echo >&2 'Database already exists with applied updates!' + exit 127 +fi + ./mg-schema-update $quietopt check-user $progress "Populating database..." -- 1.7.10.4 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
