Spring Application Advisor Recommends Incompatible Spring Cloud Versions Due to Incorrect Mapping
Article ID: 451783
Updated On:
Products
Issue/Introduction
Spring Application Advisor utilizes an internal upgrade mapping catalog to generate safe, aligned upgrade plans for Spring Boot and Spring Cloud environments. In scenarios where this mapping catalog contains incorrect or outdated definitions, the Advisor may suggest an upgrade path for Spring Cloud dependencies that contradicts official Spring compatibility documentation. This article details the symptoms of these incorrect recommendations, how to verify compatibility, and the process for reporting mapping discrepancies to Broadcom Support to ensure alignment with Spring Boot 3.x and 4.x baselines.
- Example for a repo which is on Spring Boot 3.5.13 which is compatible with Spring Cloud 2025.0.x as outlined in the Spring Docs
- However App advisor is specifying upgrade to Spring Cloud 2025.1.1 which is not compatible with Spring Boot 3.5.13:
Environment
- VMware Tanzu Platform Spring
- Spring App Advisor 1.6.x
- Spring Boot 3.x and 4.x
- Spring Cloud 2025.x
Cause
The Spring Application Advisor relies on an internal upgrade mapping catalog to ensure dependency alignment. Incorrect version suggestions occur when required upgrade mappings in this catalog are missing, incomplete, or incorrectly defined. By design, Advisor prioritizes safety; if it cannot guarantee dependency alignment or if the internal mapping is invalid, it may output an incorrect suggestion or refuse to generate a plan to prevent unsupported combinations.
In Spring Cloud Gateway 2025.0, there were Module and Starter name additions and deprecations, leading to this incorrect version report.
Resolution
The Spring Cloud Gateway Release Notes for 2025.0 detail the new Module and Starter names along with the deprecated names for reference. These can be migrated using the spring-boot-properties-migrator as detailed in the release notes.
Resolution for this will be released in a future Major release of Spring Cloud Gateway
- Verify the official .
- If the Advisor recommendation deviates from the official matrix, collect the
build-config.jsonand the full Advisor command output. - Open a support ticket with Broadcom Support.
- Provide the gathered configuration and logs. Broadcom Support will validate the mapping and provide an official workaround or deliver an updated mapping via a patch release.
- To speak with a customer representative or a Support Engineer, see Contact Support.
Note: The Advisor provides an advanced option to apply upgrades even when dependency alignment cannot be guaranteed: advisor upgrade-plan apply --accept-no-alignment. Use this option with caution for evaluation purposes only; it is not a replacement for resolving missing or incorrect upgrade mappings.
Additional Information
Feedback
