Harbor Tile deployment from EPMC fails after integrating the Wavefront

Products

• VMware Tanzu Kubernetes Grid

Issue/Introduction

Symptoms:

• Harbor 2.1.1 installation from EPMC fails.

• When you check the Bosh task for failed deployment, you see the entries similar to:
  Expected task '38' to succeed but state is 'error'
  Exit code 1
  Task 38 | 06:52:27 | Updating instance harbor-app: harbor-app/b7bb70eb-64d7-4c2f-9825-7b7de1950a08 (0) (canary) (00:09:52)
  L Error: 'harbor-app/b7bb70eb-64d7-4c2f-9825-7b7de1950a08 (0)' is not running after update. Review logs for failed jobs: wavefront, harbor, bosh-dns, bosh-dns-resolvconf, bosh-dns-healthcheck, system-metrics-agent, harbor-enable-bosh-dns
  Task 38 | 07:02:19 | Error: 'harbor-app/b7bb70eb-64d7-4c2f-9825-7b7de1950a08 (0)' is not running after update. Review logs for failed jobs: wavefront, harbor, bosh-dns, bosh-dns-resolvconf, bosh-dns-healthcheck, system-metrics-agent, harbor-enable-bosh-dns

• When you ssh to the Harbor vm, you see that Wavefront service is in Stopped state:
  sudo -s
  alias docker='/var/vcap/packages/docker/bin/docker -H unix:///var/vcap/sys/run/docker/dockerd.sock'
  alias docker-compose='/var/vcap/packages/docker-compose/bin/docker-compose -H unix:///var/vcap/sys/run/docker/dockerd.sock -f /var/vcap/packages/harbor-app/docker-compose.yml '
  alias monit='/var/vcap/bosh/bin/monit'
  
  #monit summary
  <wavefront is stopped>

• When you inspects the Docker images, you don’t see the telegraf:1.11.3 & wavefronthq/proxy:4.38  images.

Environment

VMware PKS 1.x

Resolution

This is a known issue impacting Harbor tile 2.0.1, 2.0.2, 2.0.3, 2.1.0, 2.1.1 versions.

Workaround:

To work around this issue, tag the existing Telegraf & wavefront docker image versions as below:
docker tag  telegraf:1.14 telegraf:1.11.3
docker tag  wavefronthq/proxy:5.7 wavefronthq/proxy:4.38
Then click apply-changes from OpsManager to install the Harbor.