Applying vIDM 3.3.7 CSP Patch fails during 'Patch Postgres Cluster' with error "Error code: LCMVIDM71147"
search cancel

Applying vIDM 3.3.7 CSP Patch fails during 'Patch Postgres Cluster' with error "Error code: LCMVIDM71147"

book

Article ID: 449252

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite) VMware vRealize Suite Lifecycle Manager 8.x

Issue/Introduction

  • Applying vIDM 3.3.7 CSP Patch fails during the step 'Patch Postgres Cluster' with the following errors:

Error code: LCMVIDM71147

Failed to update Auth provider with VMware Aria Suite Lifecycle hostname

Failed to login to VMware Identity Manager vIDM_FQDN. Failed to get admin token: Organization does not exist

  • The "saas.OAuth2RefreshToken" database table is greater than 7GB in size

NOTE - To verify "saas.OAuth2RefreshToken" database size follow steps 1-3 in the Resolution section for this KB

 

Environment

vIDM 3.3.7

Cause

This issue occurs due to the /db partition running out of space while the Postgres version is being upgraded during the Patch Postgres Cluster step. The "saas.OAuth2RefreshToken" table is not able to be copied over to the new Postgres version due to no space left on device

Resolution

To resolve this issue perform the following steps below:

1. Revert to a clean snapshot/backup for the vIDM nodes

2. Clean up the OAuth2RefreshToken database table on the vIDM nodes following the steps in vIDM 3.3.x vPostgres DB OAuth2RefreshToken table consumes most space on the appliance leading to service outages.

3. Patch the vIDM systems once again following instructions outlined in the patching process

NOTE - If after cleaning up the OAuth2RefreshToken database table on the vIDM nodes and the patching process fails again with error code LCMVIDM71147 follow the steps in Running sync task to update the current host name or FQDN of VMware Aria Suite Lifecycle with VMware Identity Manager fails with error LCMVIDM71147. After performing the steps in the KB, 'Retry' the failed task from Aria Suite Lifecycle Manager once again.

Additional Information

You can troubleshoot upgrade problems by reviewing the error logs. If Directories Management does not start, you can revert to a previous instance by rolling back to a snapshot.