TMC Package Reconcile fails with the error "Expected to find at least one version, but did not" after migrating from TMC SaaS to Self-Managed
search cancel

TMC Package Reconcile fails with the error "Expected to find at least one version, but did not" after migrating from TMC SaaS to Self-Managed

book

Article ID: 418659

calendar_today

Updated On:

Products

VMware Tanzu Mission Control

Issue/Introduction

  • After migrating a managed Kubernetes cluster from a Tanzu Mission Control (TMC) SaaS environment to a TMC Self-managed environment, specific installed packages fail to reconcile.

  • The package reconciliation process, typically managed by kapp-controller within the cluster, produces the following error message in the package installation status:

"Reconcile failed: Expected to find at least one version, but did not."

  • This error signifies that the package manager cannot locate the manifest or metadata for the currently installed package version within the newly configured package repositories of the TMC Self-managed instance.

  • To confirm the issue, inspect the contents of the package repository resource in the affected namespace:

Execute the following kubectl command, replacing <name_space> with the appropriate namespace: 

kubectl get pkg -n <name_space>

Review the output and confirm that the package version currently installed on the cluster (the version expected to reconcile) is not listed in the available versions within the Repository resource's status.

Environment

  • Tanzu Mission Control - Self Managed

Cause

  • The primary cause is the missing package version in the package repositories configured for the TMC Self-managed environment. Packages installed by the SaaS environment are usually pinned to a specific, immutable version. The repositories configured in the new Self-managed instance may not contain the exact version of the package that was installed previously.

Resolution

  • The recommended solution is to update the installed package to a version that is actively listed and available in the configured package repositories within the TMC Self-managed environment. This process ensures that the kapp-controller can successfully find the required package manifest and align the installed state with the available versions.

  • Refer to the techdoc below for detailed steps on editing the installed package version.
    Edit an Installed Package