db tables are not created with the expected charset/engine

[Brent Eagles]

In mariadb, the database tables are created with the default charset and engine instead of the expected utf8 and InnoDB, respectively.

[OpenStack Infra (hudson-openstack)]

Change abandoned by "Brent Eagles <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/designate/+/901135

[Brent Eagles (beagles)]

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.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/designate/+/901135
Committed: https://opendev.org/openstack/designate/commit/1f045ee64a27c6208b3dc2a6bf5b9c5027342235
Submitter: "Zuul (22348)"
Branch: master

commit 1f045ee64a27c6208b3dc2a6bf5b9c5027342235
Author: Brent Eagles <email address hidden>
Date: Thu Nov 16 09:33:53 2023 -0330

    Add charset and engine parameters to alembic create tables

    This patch enforces utf8 and InnoDB when creating tables in
    mariadb/mysql.

    Closes-Bug: #2043701

    Change-Id: I7afb533bd2d19dfaa900e3b946dc1e3563cc5198

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/designate 18.0.0.0rc1 release candidate.