MariaDB's table storage format change is causing errors after a FFU
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
In Progress
|
High
|
Damien Ciabrini |
Bug Description
In Queens - which uses MariaDB 10.1 - the internal storage format used
for InnoDB tables is the 'COMPACT' format [1]. Whereas in Train -
which uses Mariadb 10.3 - the default storage format has changed from
'COMPACT' to 'DYNAMIC'. This means the Openstack tables internally use
different storage format whether they are created in Queens or in
Train.
During an FFU from Queens to Train, the database's internal tables
are upgraded with mysql_upgrade, but that tool doesn't ALTER the
Openstack tables to use the new default internal storage format
as it is not needed when upgrading the database.
Mariadb 10.3 has more DDL checks that Mariadb 10.1, such as for example
stricter table create/alter checks and table size checks. And recent
Mariadb (e.g. 10.3.27) has changed the severity of some of those checks
when InnoDB strict mode is enforced (the default). Consequently,
some checks are failing with a few OpenStack tables after the FFU
has upgraded the database without changing the row format in use, which
at least breaks some db_sync containers:
[root@
2020-
2020-
2020-
2020-
2020-
2020-
2020-
2020-
You have to change some columns to TEXT or BLOBs')
2020-
2020-
2020-
Changed in tripleo: | |
milestone: | wallaby-2 → wallaby-3 |
Changed in tripleo: | |
milestone: | wallaby-3 → wallaby-rc1 |
Changed in tripleo: | |
milestone: | wallaby-rc1 → xena-1 |
Changed in tripleo: | |
milestone: | xena-1 → xena-2 |
Changed in tripleo: | |
milestone: | xena-2 → xena-3 |
https:/ /review. opendev. org/c/openstack /puppet- tripleo/ +/766971