Replacing VCF Automation Certificate fails with error code "LCMVCFA00007" in VCF Operations 9.1
search cancel

Replacing VCF Automation Certificate fails with error code "LCMVCFA00007" in VCF Operations 9.1

book

Article ID: 452967

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • Attempting to replace the VCF Automation (VCFA) certificate from the VCF Operations UI fails.

  • The task fails specifically during the "Push capabilities to VCF Automation" at stage 2.

  • The UI and logs display the following error:

    • Error Code: LCMVCFA00007
      Error occurred while pushing capabilities in VCF Automation
      com.vmware.vrealize.lcm.vcfa.common.exception.UnableToGetVcfaTokenException: illegal_parameter(47)

  • Despite the task failure in VCF Operations, the certificate is successfully replaced in the background, and the VCF Automation component shows the new certificate as "Active".

Environment

VCF Operations 9.1

VCF Automation 9.1

Cause

Internal communication between VCF Operations and VCF Automation is incorrectly being routed through the globally configured HTTP proxy. Because the global proxy cannot reach or resolve these internal VCF components, the connection fails, which causes the capability push task to fail during the certificate replacement workflow.

Resolution

Broadcom is aware of this issue. A fix has been identified and will be included in the upcoming release.

Workaround

To bypass this issue and successfully complete the certificate replacement in VCF 9.1, temporarily disable the global HTTP proxy:

  1. In the VCF Operations UI, navigate to Operations Console > Administration > Global Settings > Global Proxy.

  2. Take note of the current proxy configuration, and then temporarily delete the proxy settings.

  3. Navigate back to the failed VCFA certificate update task and Retry it.

  4. Allow the task to complete successfully.

  5. Once the certificate has been applied, return to Global Proxy settings and re-configure/re-enable the proxy using the details noted in step 2.