Comment 2 for bug 2043701

The title and summary are inaccurate. The issue lies in one of the alembic migration steps altering the database to default charset to utf8 after some tables had already been created. This ends up establishing a hard requirement on the default charset set on designate's database.

The problem was identified when the alembic version that created the shared_zones table failed because of a charset mismatch when creating a foreign key constraint with the zones id in the zones table.