After upgrade to mariadb 10.3, tables are not converted to new default row format
Bug #1913438 reported by
Damien Ciabrini
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Confirmed
|
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:/
We'd need a hook during the upgrade that would allow us to perform specific DB upgrade tasks at the right time.
Revision history for this message
| Sofer Athlan-Guyot (sofer-athlan-guyot) wrote | #1 |
| Changed in tripleo: | |
| milestone: | wallaby-2 → wallaby-3 |
| Changed in tripleo: | |
| milestone: | wallaby-3 → wallaby-rc1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/tripleo-heat-templates 13.2.0 | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/tripleo-heat-templates 11.5.0 | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/tripleo-heat-templates 12.4.3 | #4 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/tripleo-heat-templates 14.1.0 | #5 |
| Changed in tripleo: | |
| milestone: | wallaby-rc1 → xena-1 |
| Changed in tripleo: | |
| milestone: | xena-1 → xena-2 |
| Changed in tripleo: | |
| milestone: | xena-2 → xena-3 |
To post a comment you must log in.
This could affect update as well for a user coming from 13->16 without https:/
Then during update we cloud have the old compact structure and fail ?