Comment 14 for bug 993663

Ran through two verifications, one on a single node virtual instance with mysql and nova-api running locally and another on a live mulit node cluster with running instances and a populated database.

Overview of the latter captured here:

After deployment and configuration of nova packages 2012.1-0ubuntu2.3.

Before upgrade, verification of bug:

(...on mysql server)
# mysql -u root
mysql> create database test_nova;
mysql> grant all privileges on test_nova.* to 'nova'@'localhost' identified by 'nova';
mysql> Bye
# mysqldump -u nova -p nova > nova-backup-1.sql
Enter password:
# mysql -u nova -p test_nova < nova-backup-1.sql
Enter password:
ERROR 1005 (HY000) at line 1071: Can't create table 'test_nova.projects' (errno: 150)

After upgrade, verification of fix:

(...on Nova node, precise-proposed enabled.)
~# apt-get upgrade
~# dpkg -l | grep nova-common
ii nova-common 2012.1+stable~20120612-3ee026e-0ubuntu1 OpenStack Compute - common files
~# nova-manage db sync
2012-07-02 16:30:00 AUDIT nova.db.sqlalchemy.fix_dns_domains [-] Applying database fix for Essex dns_domains table.
(...on mysql server)
# mysqldump -u nova -p nova > nova-backup-2.sql
Enter password:
# mysql -u nova -p test_nova < nova-backup-2.sql
Enter password:

The database can be successfully restored from a backup. I've also verified there are no adverse affects post-upgrade in terms of usability of the cloud (instances still spawn, security groups can be created, floating IPs associated, API requests serviced fine, etc)