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).
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Andrew | T237749 Upgrade wmcs OpenStack version to Ocata | |||
| Resolved | Andrew | T210715 cloudvps: PDNS 3.x vs 4.x | |||
| Open | None | T132225 Add SSHFP dns records to bastions | |||
| Resolved | MoritzMuehlenhoff | T224549 Track remaining jessie systems in production | |||
| Open | None | T224708 Drop most of mwopenstackclients.DnsManager in favour of designateclient | |||
| Resolved | aborrero | T212302 CloudVPS: upgrade: jessie -> stretch & mitaka -> newton | |||
| Resolved | Andrew | T234834 Various user visible errors in Cloud VPS projects following OpenStack upgrade on 2019-10-07 | |||
| Invalid | None | T192156 Review encoding of all OpenStack databases | |||
| Resolved | Andrew | T242766 upgrade cloud-vps openstack to Openstack version 'Queens' | |||
| Duplicate | None | T234830 CloudVPS: m5-master databases for openstack may require re-encoding |
Event Timeline
Comment Actions
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 🦄.
Comment Actions
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.
Comment Actions
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)
Comment Actions
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.