ERROR: "Failed to delete canceled alerts due to error: Alert filtered because of lack of privilege"
search cancel

ERROR: "Failed to delete canceled alerts due to error: Alert filtered because of lack of privilege"

book

Article ID: 445113

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

  • Attempting to delete canceled alerts as a local administrator in UI results in the following error:
    "Failed to delete canceled alerts due to error: Alert filtered because of lack of privilege".
  • This behavior occurs after updating VCF Operations to 9.1.
  • The vcops-upgrade.log contains entries similar to: 
    ####-####-####T#### INFO #### [####@#### threadId="####"] [root - upgradeutil - mergeProps] - Checking new key: "Failed.to.delete.canceled.alerts.due.to.error..%1", value: "Failed to delete canceled alerts due to error: %1".
  • The web.log and vcops-bridge-####.log reflect the same error message seen in the user interface.

Environment

VCF Operations 9.1

Cause

This issue is known to Broadcom.

Resolution

This issue will be resolved in a future minor release. Workarounds are available to manage canceled alerts until the permanent fix is released.

Workaround 1: Decrease the Alert Retention Period

Changing the retention period clears old entries automatically. To modify these settings:

  1. In the VCF Operations navigation bar, click Operate.
  2. In the left navigation pane, click Administration > Global Settings.
  3. Click the Data Retention category.
  4. Decrease the retention period value from the default 45 days to (i.e. 1 day).
  5. Allow the alerts to be naturally deleted from the system
  6. Increase or revert the data retention setting as needed

See Modifying Global Settings for more configuration details.

Workaround 2: Deactivate High Availability

Deactivating High Availability (HA) allows the removal of unwanted canceled alerts. To deactivate high availability:

Note: Create offline snapshots of all cluster nodes and cloud proxies - Snapshot Creation in VCF Operations
  1. In a web browser, navigate to the VCF Operations primary node administration interface: https://primary-node-fqdn-or-ip-address/admin
  2. Enter the administrator user name of admin.
  3. Enter the administrator password and click Log In.
  4. Click Deactivate HA and follow the steps in the interface.
  5. Wait for the process to complete. The deactivation timeline depends on cluster size and data retention period.
  6. Validate that you are now able to delete alerts from the standard UI with a local admin account
  7. Activate HA from the admin UI as needed

See Configure a VCF Operations Cluster for High Availability for cluster configuration details.

Additional Information

How to subscribe to Broadcom Knowledge Base articles