Hi tomsommer , thanks for bringing this to our attention. We believe it is a legitimate bug, I’ve filed a JIRA to have it fixed in a later release. For now your workaround is the correct approach to mitigate the upgrade to Percona Server 5.7.17-13. All the best,