-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.1.1, 8.0.4, 8.0.5, 8.1.2, 8.0.6, 8.2.0, 8.1.3, 8.0.7, 8.1.4, 8.2.1, 8.1.5, 8.2.2, 8.1.6, 8.0.8, 8.1.7, 8.2.3
-
Component/s: Database (MySQL)
-
None
-
Severity 3 - Minor
Issue Summary
Health Check for MySQL 8.0.29 fails after upgrading MySQL to 8.0.29.
Steps to Reproduce
- Use Bamboo MySQL 8.0.23 or older versions
- Upgrade MySQL to 8.0.29
- Go to Troubleshooting and Support Tools >> Instance health page and see the fail health check for MySQL collation
Expected Results
The Health Check should pass in case MySQL version is 8.0.29 which has the utf8m3 as the new display name for uft8 collation:
The server now uses utf8mb3 in place of the alias utf8 for character set names when populating data dictionary tables from built-in character sets. This affects the display of character set and related information in the MySQL Information Schema tables listed here:
More information can be found on MySQL 8.0.29
Actual Results
The below error is thrown in the atlassian-bamboo.log file:
WARN [MySQLChecksImpl] query - SELECT DEFAULT_CHARACTER_SET_NAME FROM information_schema.SCHEMATA S WHERE schema_name = ? AND DEFAULT_CHARACTER_SET_NAME != 'utf8mb4' AND DEFAULT_CHARACTER_SET_NAME != 'utf8'; WARN [MySQLChecksImpl] found unexpected result: utf8mb3 | ERROR [SupportHealthCheckProcess] Health check 'Character Set' failed with severity 'critical': 'Some tables or columns in the database are not using utf8 for their character set, or the default character set for the database is incorrect.'
Workaround
Manually disable the Database Character Set Health Check on Troubleshooting and Support Tools >> Instance health page.
- mentioned in
-
Page Loading...
- relates to
-
BDEV-17112 Loading...