Skip to main content

 

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.



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.



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.

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.

Resolution

This issue is resolved in VMware Aria Automation 8.13.1 available at VMware 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:
  • 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.
Error downloading catalog item '/actions/<ACTION_ID>_<PROJECT_ID>' (Error: Content provider error)
Refer: https://kb.vmware.com/s/article/93437

Actions

 Print

 Language:

Ask The Community
Get answers quickly from VMware experts in the community
Post Subject

Related Products:

  • VMware Aria Automation

Related Versions:

  • VMware vRealize Automation 8.x
  • Take Our Survey

Labels:

Comments

Post a Comment

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Post a Comment
Read more

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
Post a Comment
Read more

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...
Post a Comment
Read more