After upgrade to mariadb 10.3, tables are not converted to new default row format

Bug #1913438 reported by Damien Ciabrini on 2021-01-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
High
Damien Ciabrini

Bug Description

When upgrading an undercloud or overcloud to Train or higher, mariadb is dated to 10.3, which changes the default row format on disk from "Compact" to "Dynamic".

Even though the default format changes, the existing InnoDB tables are not migrated to this new format, which can cause further issues, as originally reported in [1]

[1] https://bugs.launchpad.net/tripleo/+bug/1908232

We'd need a hook during the upgrade that would allow us to perform specific DB upgrade tasks at the right time.

This could affect update as well for a user coming from 13->16 without https://review.opendev.org/c/openstack/puppet-tripleo/+/766971.

Then during update we cloud have the old compact structure and fail ?

Changed in tripleo:
milestone: wallaby-2 → wallaby-3
Changed in tripleo:
milestone: wallaby-3 → wallaby-rc1

This issue was fixed in the openstack/tripleo-heat-templates 13.2.0 release.

This issue was fixed in the openstack/tripleo-heat-templates 11.5.0 release.

This issue was fixed in the openstack/tripleo-heat-templates 12.4.3 release.

This issue was fixed in the openstack/tripleo-heat-templates 14.1.0 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers