Workflow logs are not visible for scheduled workflow runs in VMware Cloud Foundation Operations Orchestrator 9.0.2.0 (Build 25094178).
search cancel

Workflow logs are not visible for scheduled workflow runs in VMware Cloud Foundation Operations Orchestrator 9.0.2.0 (Build 25094178).

book

Article ID: 450173

calendar_today

Updated On:

Products

VCF Automation

Issue/Introduction

  • In a clustered deployment of VMware Cloud Foundation Operations Orchestrator 9.0.2.0 (Build 25094178), logs for scheduled workflow runs appear blank. This behavior is often intermittent, where logs may be visible in one browser session but not another
  • Log analysis shows the following error during log aggregation: ERROR vco [host='####' ... com.vmware.o11n.sdk.logs.LogCollector - Failed to get logs from node with node-id '####', requestUri=#### java.lang.NullPointerException: auth cannot be null

Environment

VCF Automation 9.0.2

Cause

 This is caused due to Orchestrator's session management logic preventing the renewal of authentication tokens during cross-node log retrieval requests. When the node handling the UI request attempts to fetch logs from a peer node, the authentication context is lost, resulting in a NullPointerException.

Resolution

A Permanent fix is targeted for an upcoming patch release of version 9.0.2.0. 

Follow these steps for immediate workarounds:

  1. Clear browser cookies for the Orchestrator endpoint to force a session refresh.
  2. Access the Orchestrator client using a private or incognito browser window.

Once the fix is officially released, download the latest patch from the Broadcom Support Portal.