Application failing when pushing, restaging, binding or unbinding application using mysql service instance 3.3.0
Article ID: 391624
Updated On:
Products
Issue/Introduction
When using or upgrade to mysql tile 3.3.0, user may encounter problem with pushing, restaging, binding or unbinding application using mysql SI with automatic scheduled backup.
There is bug with mysql 3.3.0 backup that this issue when the automatic scheduled backup failed for reasons.
See this KB for detail: https://knowledge.broadcom.com/external/article/383552
This bug issue is fixed in mysql tile 3.3.1:
- Bugfix: Backup process can exit successfully during network failures and when the backup is configured incorrectly in Tanzu Operations Manager
Environment
TAS
MySQL Tile 3.3.0
Cause
Restaging application failed to start with the following error:
[APP/PROC/WEB/0] [OUT] 2025-03-18 22:23:57.759 ERROR 43 --- [ main] o.s.boot.SpringApplication : Application startup failed
[APP/PROC/WEB/0] [OUT] org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.cloud.dataflow.server.config.web.WebConfiguration': Injection of autowired dependencies failed; nested exception is java.lang.IllegalArgumentException: Could not resolve placeholder 'vcap.services.bdx-mysql.credentials.hostname' in value "jdbc:mysql://${vcap.services.bdx-mysql.credentials.hostname}:3306/service_instance_db?enabledTLSProtocols=TLSv1.2"
MySQL service instance reports the backup failed with the following error:
[ERROR] 2025/03/14 02:00:06 backup.go:105: failed to upload artifact: failed to create ssh connection: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
The failure is due to a bug in MySQL tile 3.3.0 when using an automatic scheduled backup failed that is causing the problem.
Resolution
If you are using automatic schedule backups for SI, do not use MySQL tile 3.3.0.
If you are using MySQL tile 3.3.0 with automatic schedule backups, the short term fix:
- Restarting the 'adbr-agent' job on mysql SI to clear up the failed backup issue.
- Fixing the backup configuration so that backups do not fail.
- Disable (turn off) the failed or none working automatic schedule backups.
The permanent fix:
Upgrade to mysql v3.3.1, where we included a fix for this bug.
Bugfix: Backup process can exit successfully during network failures and when the backup is configured incorrectly in Tanzu Operations Manager
Feedback
