Page MenuHomePhabricator

CloudVPS: m5-master databases for openstack may require re-encoding
Open, LowestPublic

Description

When upgrading neutron database schema from Mitaka to Newton, we had several encoding issues related to latin1.

We may need to re-encode the database to something more sensible (like utf8 or whatever).

Event Timeline

aborrero triaged this task as High priority.Oct 7 2019, 3:36 PM
aborrero created this task.
aborrero moved this task from Inbox to Important on the cloud-services-team (Kanban) board.
Marostegui moved this task from Triage to In progress on the DBA board.Oct 7 2019, 3:37 PM
Penggang1 set Due Date to Oct 7 2019, 4:00 PM.Oct 7 2019, 4:09 PM
Penggang1 removed Due Date.
Penggang1 removed subscribers: Aklapper, Krenair, Bstorm and 7 others.
bd808 added a comment.Oct 8 2019, 4:19 PM

utf8 is probably not the 'right' encoding. Mysql's utf8 is only capable of 3-byte code points. latin1 and utfmb4 would both work for 4-byte code points like 🦄.

Andrew renamed this task from CloudVPS: m5-master databases for openstack may require re-enconding to CloudVPS: m5-master databases for openstack may require re-encoding.Oct 15 2019, 4:37 PM
aborrero lowered the priority of this task from High to Lowest.Dec 19 2019, 10:16 AM
aborrero moved this task from Important to Graveyard on the cloud-services-team (Kanban) board.

Lowering priority of this task. We did the Newton->Ocata upgrade (T237749: Upgrade wmcs OpenStack version to Ocata) without seeing any issue related to this.

Should we close it for now instead?

Removing the DBA tag as there is no actionable for us here so far. Please add us back if you finally think this is needed.
(I will keep subscribed to the task just in case I am needed)

During the Ocata->Pike upgrade we ran into some wrinkles with the neutron schema upgrade -- "Foreign key constraint is incorrectly formed" I worked around those by hacking in

mysql_default_charset='latin1'

for each table create. That suggests that something is messed up with that database; whatever the default encoding for new tables is disagrees with the existing coding of old tables.