Harbor-JobService in crashback loop state due to ReconcileFailed "kapp: Error: waiting on reconcile" "has timed out progressing"
search cancel

Harbor-JobService in crashback loop state due to ReconcileFailed "kapp: Error: waiting on reconcile" "has timed out progressing"

book

Article ID: 408702

calendar_today

Updated On:

Products

VMware vSphere Kubernetes Service

Issue/Introduction

You attempted to install a new Harbor Supervisor Service.

You check the status of the Harbor Supervisor Service install:

From vSphere UI > Workload Management > Supervisors > Configure > Supervisor Services > Overview

The Status column shows Error(1)

When clicking on Error(1), you see the following error:

Reason: ReconcileFailed. Message: kapp: Error: waiting on reconcile deployment/harbor-jobservice (apps/v1) namespace: s vc-harbor-domain-c#: Finished unsuccessfully (Deployment is not progressing: ProgressDeadlineExceeded (message: ReplicaSet "harbor-jobservice-##########" has timed out progressing.)).

You show the error in Supervisor Services for Harbor regarding ReconcileFailed with a timeout. And it is timing out while accessing the v2.0/internalconfig endpoint

Looking at the kube-apiserver audit logs, you see similar error like the following:

Reason: ReconcileFailed. Message: kapp: Error: create deployment/harbor-core (apps/v1) namespace: svc-harbor-domain-c##: Creating resource deployment/harbor-core (apps/v1) namespace: svc-harbor-domain-c##: API server says: Deployment in version "v1" cannot be handled as a Deployment: json: cannot unmarshal string into Go struct field DeploymentSpec.spec.replicas of type int32 (reason: BadRequest)

Environment

  • vSphere Kubernetes Service
  • Harbor Supervisor Service

Cause

The error unmarshal string into Go struct field indicates a malformed or incorrectly submitted values.yaml file.

Resolution

  • Check the format and structure of the values.yaml
  • Correct any character alignment
  • Re-apply the values.yaml