VMware vRealize Operations Management Pack for VMware vRealize Orchestrator | 17 OCT 2019 | Build 14793530

What's in the Release Notes

The release notes cover the following topics:

Introduction

Management pack for vRealize Orchestrator (vRO) provides access to the vRealize Orchestrator workflows for remediation of actions and the ability to launch workflows directly from the vRealize Operations user interface. 

What's New

  • Execution of dynamic/custom workflows as an action on the related objects
  • Ability to execute the action on custom groups

Highlights

  • Discover vCenter workflows and user defined workflows
  • Auto remediation associated with alerts of vRealize Operations
  • Correlation between vRealize Orchestrator workflows and the recommendations/alerts of vRealize Operations
  • Supported actions on Custom Groups
  • Support to invoke Custom Workflows on vCenter related Objects

Compatibility

For compatibility between products, please refer to the VMware Product Interoperability Matrices.

Known Issues

  • When you view the vRealize Orchestrator Workflows Overview dashboard, the Number of Success and Failed Executions widget shows no data.

    When you view the vRealize Orchestrator Workflows Overview dashboard, the Number of Success and Failed Executions widget
    shows no data. This is because the collection time is set to 720 minutes by default. 

    Workaround: Configure the adapter instance Workflow Execution Metric Collection Time such that it falls in the widget time frame. For example, 6 * 60 = 360 Minutes.

  • Executing workflow for multiple objects is not supported in the vRealize Orchestrator adapter.

    You cannot execute workflows for multiple objects in vRealize Orchestrator adapter as it is not supported. 

  • In vRealize Operations Manager, the icons for out of the box worflows are not displayed in the upgraded environment. 

    When you view a list of workflows in vRealize Operations Manager the icons for out of the box worflows are not displayed in the vRealize Operations environment. 

  • The Execute Workflow Action lists vCenter instances that are not configured in vRealize Orchestrator.

    In vRealize Operations Manager lists all the vCenter instances while Execute Workflow Actions on a vCenter instance even though those are not configured in vRealize Orchestrator.

  • The vrops_alert_id for custom workflows is not displayed in the UI

    The vrops_alert_id for custom workflows is not displayed in the UI. However, the alert id is sent in the backend along with the workflow when the user triggers an action on the alert.

    Workaround: None

check-circle-line exclamation-circle-line close-line
Scroll to top icon