SQL Mode
Starting with MySQL 5.7 the default SQL mode is far more strict then it was before.
It now includes ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, NO_AUTO_CREATE_USER, and NO_ENGINE_SUBSTITUTION.
This can cause problems for applications which need other SQL modes. Apache CloudStack is one of these applications.
The best thing would be to modify the SQL queries executed by CloudStack, but that’s not that easy.
Changing the mode
Luckily the SQL mode can be changed in either the my.conf or as a session variable.
In the my.cnf one can add:
[mysqld] sql_mode = 'STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'
Or modify the /etc/cloudstack/management/db.properties file to include this line:
db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true&sessionVariables=sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'
You should now be able to run a CloudStack management server on MySQL 5.7!
Future
In the future CloudStack should only be using SQL queries which comply with the new more strict SQL mode. In the meantine a issue and Pull Request have been created to track this situation.