ovs-ctl: Log messages about database upgrade process.
authorBen Pfaff <blp@nicira.com>
Thu, 7 Jul 2011 19:31:58 +0000 (12:31 -0700)
committerBen Pfaff <blp@nicira.com>
Tue, 26 Jul 2011 16:04:10 +0000 (09:04 -0700)
This should make problems easier to debug.

Bug #6280.

utilities/ovs-ctl.in

index c783f3da85c96215e813061527f9c4f5e3e75f9a..a5ef56ad973fb3b062d66fa0df95264902e29250 100755 (executable)
@@ -71,7 +71,8 @@ upgrade_db () {
         # Back up the old version.
         version=`ovsdb_tool db-version "$DB_FILE"`
         cksum=`ovsdb_tool db-cksum "$DB_FILE" | awk '{print $1}'`
-        cp "$DB_FILE" "$DB_FILE.backup$version-$cksum"
+        backup=$DB_FILE.backup$version-$cksum
+        action "Backing up database to $backup" cp "$DB_FILE" "$backup"
 
         # Compact database.  This is important if the old schema did not enable
         # garbage collection (i.e. if it did not have any tables with "isRoot":
@@ -82,10 +83,10 @@ upgrade_db () {
         # does) would cause the record to be dropped by the first transaction,
         # then the second transaction would cause a referential integrity
         # failure (for a strong reference).
-        ovsdb_tool compact "$DB_FILE"
+        action "Compacting database" ovsdb_tool compact "$DB_FILE"
 
         # Upgrade or downgrade schema.
-        ovsdb_tool convert "$DB_FILE" "$DB_SCHEMA"
+        action "Converting database schema" ovsdb_tool convert "$DB_FILE" "$DB_SCHEMA"
     fi
 }