Scheduler failure after upgrading to MySQL 3.0

Products

• VMware Tanzu SQL

Issue/Introduction

After upgrading to MySQL 3.0, users are unable to create or delete scheduler service instances. This error is returned when attempting to create a new scheduler service instance:

The service broker returned an invalid response. Status Code: 500 Internal Server Error, Body:

The above error indicates service instance creation fails but does not reveal why. Scheduler broker logs will need to be analyzed to find more relevant information about the failure. Scheduler broker logs can be found in the system org/ scheduler space.

This error message is found in Scheduler broker logs

"level":"error","ts":1685353517.0341816,"caller":"handlers/deprovision.go:55","msg
":"Deprovision Handler:Failure to deprovisionError 1231: Variable 'sql_mode' can't
be set to the value of 'NO_AUTO_CREATE_USER'","stacktrace":"pcf-scheduler/broker/web/handlers.DeprovisionH
andler.ServeHTTP

MySQL v3.0 introduces support for MySQL 5.7 and 8.0. 

”NO_AUTO_CREATE_USER” is enabled by default in MySQL 5.7.
”NO_AUTO_CREATE_USER” is not supported in MySQL 8.0.

Environment

Product Version: Other

Resolution

A workaround to resolve this failure is to restart the scheduler broker and scheduler apps. This issue will be fixed in a future release of the Scheduler tile.