The deploy-scheduler errand might fail during upgrade to Scheduler v2.0 due to lower version of backend MySQL instance

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

During upgrade of Scheduler tile to v2.0 the deploy-scheduler errand might fail with error as shown below. 

2024-03-15T09:46:10.25+0530 [APP/PROC/WEB/0] OUT 2024-03-15T04:16:10.245Z ERROR 13 --- [           main] o.s.boot.SpringApplication               : Application run failed
2024-03-15T09:46:10.25+0530 [APP/PROC/WEB/0] OUT org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Flyway Teams Edition or MySQL upgrade required: MySQL 5.7 is no longer supported by Flyway Community Edition, but still supported by Flyway Teams Edition.

The message "MySQL upgrade required: MySQL 5.7" indicates that the backend MySQL instance is still running on version 5.7 which is no longer supported by Scheduler 2.0. This is also mentioned as Breaking Changes in Scheduler v2.0 release note.
** MySQL version: Scheduler v2.0 contains Spring Boot v3.1.5 and thus requires a MySQL v8.0 database

In this case the MySQL for TAS tile on the foundation is still on version 3.1 and the following note can be found in the release note. 

Environment

Product Version: 4.0

Resolution

Before upgrading Scheduler tile to v2.0, firstly you need to upgrade MySQL for TAS tile to v3.2 as well as all existing MySQL service instances (including the one used by Scheduler). 
Refer to MySQL for TAS document for details about upgrading MySQL for TAS.