Telemetry tile is failing to complete Apply Changes during pre-start script for telemetry-collector job

Products

• VMware Tanzu Platform Core
• VMware Tanzu Application Service

Issue/Introduction

• During the Apply Change operation on the Telemetry tile, the telemetry-collector job fails during pre-start script:
  
  Task 406243 | 20:34:30 | L executing pre-start: telemetry_centralizer/########-####-####-####-76d78fd51f88 (0) (canary) (00:00:32)
                       L Error: Action Failed get_task: Task ########-####-####-####-209da3acd1d0 result: 1 of 4 pre-start scripts failed. Failed Jobs: telemetry-collector. Successful Jobs: bpm, bosh-dns, qualys-cloud-agent-linux.
  
  
• Checking 'bosh vms' for the pivotal-telemetry-om-<ID> deployment, you see the telemetry-centralizer instance in stopped state.
• On the pivotal-telemetry-om-<ID> VM the /var/vcap/sys/log/telemetry-collector/pre-start.stderr.log shows messages like:
  

  Error: Failed collecting from Operations Manager: Failed to retrieve pending change list from Operations Manager: failed to submit request: could not send api request to GET /api/v0/staged/pending_changes: token could not be retrieved from target url: Post "https://<OPSMAN_FQDN>/uaa/oauth/token": tls: failed to verify certificate: x509: certificate is not valid for any names, but wanted to match <OPSMAN_FQDN>

  
  
  
  

Cause

This failure occurs because the Telemetry tile is configured to use TLS Verification for data collected from Tanzu Operations Manager in the 'Telemetry Settings' section of the tile configuration and the certificate is invalid. 

Resolution

Either:

1. Update the certificate in the Telemetry Settings section on the Telemetry tile for Operations Manager to ensure it is correct, or
2. Select the 'Insecure skip TLS Verify' option in the tile configuration.