Diagnostics for VMware Cloud Foundation: Diagnostics Log Assist Troubleshooting

Products

• VCF Operations

Issue/Introduction

Diagnostics Log Assist requires the configuration of a Unified Cloud Proxy. An Unified Cloud Proxy can not be in the same Collector Group with a Classic Cloud Proxy. After you deploy your Unified Cloud Proxy(s) you must assign your inventory under Log Assist Assignments found in Infrastructure Operations → Configurations. All inventory needs to be assigned to Cloud Proxys for log assist to function. You will see grayed out check boxes in the log assist feature of any endpoints which are not associated with an Unified Cloud Proxy. 

When you initiate Diagnostics Log Assist Operations will communicate with the Unified Cloud Proxy. The Unified Cloud Proxy will validate the rights to the Product integrations and the Cloud Service. The Unified Cloud Proxy will then start collecting the log bundle from the object selected and upload these log files to the Case you have defined along with the Site ID you have configured. The log files will be streamed from the Object through the Cloud Proxy to the cloud service in ~10mb chunks of data. This process is queued so if there is a delay in writing to the Cloud Service the Log Assist job will not fail.

Environment

Operations for VMware Cloud Foundation 9.0

Resolution

This is a list of the common errors and next troubleshooting steps for Diagnostics Log Assist.

 

Error Message	Troubleshooting
No mapped cloud proxy for object.	At the time of starting the download process there wasn’t a mapping for this object (or parent) in LogAssist Assignments page
Failed to download file	Possibility 1: Concurrency issues - someone else (manually) created a log bundle and the product does not allow multiple log bundles at a time
Task with id %s is in IN_PROGRESS state more than 20 mins.	In case the worker in the cloud proxy fails and does not update successfully the state that the task is running due to connectivity issues from the CP to the Ops nodes