Ansible API is failing with 500 Error for device onboarding
search cancel

Ansible API is failing with 500 Error for device onboarding

book

Article ID: 244687

calendar_today

Updated On:

Products

CA Privileged Access Manager (PAM)

Issue/Introduction

We use Ansible to provision new devices in PAM. When this is initiated from two devices at about the same time, the "POST /api.php/v1/devices.json" Rest API call often fails with a 500 error for one of them. Sometimes the device running into the error is found in PAM afterwards, but typically not. A retry usually works.

Environment

Privileged Access Manager, releases 4.0.0-4.0.3 and 4.1.0

Cause

The Rest API calls were not fully synchronized and could step on each other.

Resolution

The code is fixed as DE532840 in the 4.0.4 and 4.1.1 releases, please upgrade to resolve the issue.

Additional Information

Resolved Issues in 4.0.4: https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/symantec-security-software/identity-security/privileged-access-manager/4-1-5/release-information/resolved-issues-in-earlier-4-x-releases/Resolved-Issues-in-4-0-4.html

Resolved Issues in 4.1.1: https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/symantec-security-software/identity-security/privileged-access-manager/4-1-5/release-information/resolved-issues-in-earlier-4-x-releases/Resolved-Issues-in-4-1-1.html