Unable to configure the tenant-app-plugin after upgrading to VMware Chargeback

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• After upgrade to VMware Chargeback 8.16 (formerly known as vRealize Operations Tenant App for VMware Cloud Director), the plugin configuration fails with the error:

Failed to read data from input stream. PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.

Environment

VMware Aria Operations 8.x

VMware vRealize Operations 8.10.x

VMware Chargeback 8.10

VMware Chargeback 8.16

Cause

If the vCloud Director certificate is not present in Chargeback cacerts , it will result in the above plugin configuration error.

Resolution

To resolve this issue, add the valid vCloud Director certificate to the Chargeback cacerts before configuring the plugin.

Note: It is required to reboot the Chargeback appliance during these steps.

1. Download the certificate from vCloud Director in .PEM format.
2. Using an SCP utility, copy the downloaded certificate to the Chargeback appliance's /tmp directory.
3. Log into the Chargeback appliance as root via SSH or Console.
4. Navigate to the /tmp directory:

cd /tmp

5. Run the following command to:

openssl x509 -in vcdcert.pem -outform pem -outform der -out cert.cer

Note: Replace vcdcert.pem with the name of the certificate file downloaded from vCloud Director.

6. Run the following command to add the certificate to the Chargeback cacerts store:

keytool -import -alias alias_name -keystore '/usr/java/jre-vmware/lib/security/cacerts' -file cert.cer

Note: Replace alias_name with the Alias you'd like to give the certificate.

Example: keytool -import -alias vcdcert -keystore '/usr/java/jre-vmware/lib/security/cacerts' -file cert.cer

Note: When prompted, enter the default password of changeit and press enter.

7. Reboot the Chargeback appliance by running the following command:

reboot
 

Once the Chargeback appliance has finished rebooting, you can configure the plugin again after clearing the old backend extensions from vCloud Director using API explorer.