VMware Aria Automation (Formerly known as vRealize Automation) fixing the error status code 500 when Content source with ABX is created and action has its "shared" field with a NULL value
search cancel

VMware Aria Automation (Formerly known as vRealize Automation) fixing the error status code 500 when Content source with ABX is created and action has its "shared" field with a NULL value

book

Article ID: 336849

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:

VMware Aria Automation Service Broker has а content source of Type "Extensibility actions" for a certain project which contains actions, but the "Number of items" show that fewer actions are synced than the total number.  For example, 5/10 will be shown, and a red exclamation mark next to it. This means that not all actions are synced in the content source and the problematic ones will not be available for use in the Catalog.

image.png

 


Environment

VMware vRealize Automation 8.x

Cause

A change has been introduced in early versions of VMware Aria Automation (around 8.2, or even earlier) for which actions created before that version will not be possible to be used as a content source. This is due to a bug introduced in that version.

Older actions, which are created before the bug was introduced will not be accessible as a content source and a Catalog item will not be possible to be created from them.

Resolution

This issue is resolved in VMware Aria Automation 8.13.1 available at Broadcom Product downloads.


Workaround:

Prerequisites

  1. Log in to VMware Aria Automation.
  2. Go to Service Broker > Content Sources.
  • If clicked on the red exclamation mark in the content source, a pop-up will appear with each action that has caused the sync to fail. The error message will be something like the following:
Error downloading catalog item '/actions/<ACTION_ID>_<PROJECT_ID>' (Error: Content provider error).
  • Using this, the action can be identified by its "ACTION_ID" and "PROJECT_ID". Users can use these after that to go to the action edit page, which is:

https://<ARIA_AUTOMATION_HOSTNAME>/automation-ui/extensibility-ui;ash=%2Factions%2Flist%2Fedit%3Bid%3D<ACTION_ID>%3BprojectId%3D<PROJECT_ID>


Workaround

For each of the problematic actions:

  1. Open its Edit page
  2. Click on SETTINGS in the upper left corner
  3. Double-click on Share with all projects in this organization. Do not do it too fast, wait for the checkbox to actually get checked or unchecked and then return it to its original state.
  4.  Click on APPLY.
  5. Click on SAVE in the bottom left corner.
  6. Repeat prerequisites and steps 1 to 5 for each of the problematic actions.
  7.  After has been done for all the actions go to the details page of the content source which has the red mark, and do the following:
  • Click on VALIDATE.
  • Click on SAVE.
  1. Validate the results: after a few seconds, all actions should be synced and there should not be a red exclamation mark anymore. The actions should be available for usage.


Additional Information

Impact/Risks:

Older actions, which are created before the bug was introduced will again be accessible as a content source and a Catalog item will be possible to be created from them.