Upgrade Planner fails on Scheduler with error "Target versions you've selected have dependencies that are not met"
search cancel

Upgrade Planner fails on Scheduler with error "Target versions you've selected have dependencies that are not met"

book

Article ID: 298407

calendar_today

Updated On:

Products

VMware Tanzu Application Service for VMs

Issue/Introduction

There is an issue when targeting Scheduler 1.6.3+ in Upgrade Planner that blocks generating the plan with following error
 
Error:
Target versions you've selected have dependencies that are not met, according to our metadata. Please check your entries and dependencies on Tanzu Network.
   Scheduler requires
      Java Buildpack 4.49.*, 4.50.*, 4.51.*, 4.52.*, 4.53.*, 4.54.*, 4.55.*, 4.56.*, or 4.57.*

Please check your entries and dependencies on Tanzu Network and update your plan accordingly.

This error will be shown even if you have targeted a TAS version that does met the Java Buildpack dependency.  E.g. You have targeted TAS 2.13.19, that is shipped with 4.56, which is in the dependency list.



Environment

Product Version: 2.13

Resolution

The workaround for this is to add Java Buildpack pack in "Manually Add Tiles" section and select a version that meets the dependency in both Current and Target version. E.g 4.49.1. This will bypass the lock and allow to generate a plan.

Please, notice that there is another issue in Upgrade Planner and Java Buildpack that only shows versions with 3 digits. E.g It will show 4.49.1, but not 4.56. There is a dedicated KB article that explains this issue in detail.

Summarizing. This issue has 2 parts:

  • One is that Upgrade Planner shows there is a dependency not met, when it's actually met.
  • The other is that when adding Java Buildpack to workaround the above issue, it only shows versions with 3 digits.