Telegraf agent plugin deletion fails with error "DEACTIVATION_FAILED" or "Minion did not return" in VCF Operations
search cancel

Telegraf agent plugin deletion fails with error "DEACTIVATION_FAILED" or "Minion did not return" in VCF Operations

book

Article ID: 453167

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

When attempting to delete or deactivate a Telegraf process plugin (e.g., processavailability) from an endpoint in VMware VCF Operations, the task fails.

The UI reports the task status as DEACTIVATION_FAILED. Reviewing the analytics logs (/storage/log/vmware-vrops-cprc/cprcDockerHelper.py.log or actions-data) shows errors similar to:

  • Plugin update task failed at [timestamp] with value DEACTIVATION_FAILED

  • Minion did not return. [No response] salt-run jobs.lookup_jid

  • ERROR: Minions returned with non-zero exit code

Environment

  • VCF Operations 9.0.x
  • VCF Operations 9.1.x

Cause

In high-latency or slow network environments, the default Salt API execution timeout is not properly set during plugin configuration tasks (defaulting to -t 0). As a result, the Salt Master command times out before receiving a response back from the Salt Minion, causing the deactivation/delete task to fail.

Resolution

The issue will be fixed in the future release of VCF Operations 9.1.x

For workaround, open a support request with Broadcom Support and refer this KB.