Harbor stuck in initiated state

Products

• VMware Telco Cloud Automation

Issue/Introduction

The status of the harbor partner system shows as 'initiated'.

Environment

2.3

Cause

This can be encountered during upgrades of the platform.
If TCA and Harbor have been upgraded but the Kubernetes clusters have not, then this status will be expected.

Resolution

This will not prevent the clusters from upgrading.
Upgrade the clusters per the normal procedure.
If there are no issues, the status will change to 'Connected' as expected.
If there are issues, additional troubleshooting will be necessary and this status will not be due to being mid-upgrade.