** Changed in: kolla-ansible/train
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1856296
Title:
upgrade to Train might fail due to mariadb row format
Status in kolla-ansible:
Invalid
Status in kolla-ansible train series:
Fix Released
Status in kolla-ansible ussuri series:
Invalid
Status in OpenStack Compute (nova):
Invalid
Bug description:
In kolla-ansible CI we started getting on Ubuntu for Stein->Train:
Row size too large. The maximum row size for the used table type, not
counting BLOBs, is 8126. This includes storage overhead, check the manual. You
have to change some columns to TEXT or BLOBs
for "ALTER TABLE instances ADD hidden BOOL" in nova upgrade
This is due to the following:
...
If the table is using either the REDUNDANT or the COMPACT row format, then
one potential solution to this problem is to convert the table to use the
DYNAMIC row format instead.
If your tables were originally created on an older version of MariaDB
or MySQL, then your table may be using one of InnoDB's older row
formats:
In MariaDB 10.1 and before, and in MySQL 5.6 and before, the COMPACT row
format was the default row format.
...
from
https://mariadb.com/kb/en/library/troubleshooting-row-size-too-large-errors-with-innodb/#solving-the-problem
Indeed, the Stein images for Ubuntu include MariaDB 10.1 which we had
to upgrade in Train due to other incompatibilities (with neutron).
It is also worth noting that old CentOS deployments may also have this
limited row format.
To manage notifications about this bug go to:
https://bugs.launchpad.net/kolla-ansible/+bug/1856296/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
