| 2024-06-26 09:36:14 |
Andrew Bonney |
description |
When upgrading Cinder from 539d8725258932e8a655370fa3ffc7f2eefa85b9 (2023.2) to 0ff4262fba803152e94e32e0dc8e4a2e56fcb0f5 (2024.1) we are observing a failure during the DB sync step 'Make use_quota non nullable'.
The 'cinder-manage db sync' command exits with code '1' and no output. The logs report the following traceback: https://paste.openstack.org/show/824537/
It appears the command 'ALTER TABLE volumes MODIFY use_quota BOOL NOT NULL DEFAULT true;' does not work against the existing definition '`use_quota` tinyint(1) DEFAULT NULL' given the existing data held in the column which appears to be a mix of '0', '1' and 'NULL'.
We're running MariaDB version 10.11.6 in this case. |
When upgrading Cinder from 539d8725258932e8a655370fa3ffc7f2eefa85b9 (2023.2) to 0ff4262fba803152e94e32e0dc8e4a2e56fcb0f5 (2024.1) we are observing a failure during the DB sync step 'Make use_quota non nullable'.
The 'cinder-manage db sync' command exits with code '1' and no output. The logs report the following traceback: https://paste.openstack.org/show/824537/
It appears the command 'ALTER TABLE volumes MODIFY use_quota BOOL NOT NULL DEFAULT true;' does not work against the existing definition '`use_quota` tinyint(1) DEFAULT NULL' given the existing data held in the column which appears to be a mix of '0', '1' and 'NULL'.
The traceback reports an issue with row 1 which has a column value of NULL.
We're running MariaDB version 10.11.6 in this case. |
|
