Package Creation in VCF Operations Orchestrator Fails with "500, OK" Error Banner

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• After upgrading Aria Automation Orchestrator to VCF Operations Orchestrator 9.0 or 9.1.0, attempts to create or export packages within the VCF Operations Orchestrator UI fail. The interface displays a red error banner at the top of the screen reading ! 500, OK with a secondary pink error box reading [object Object].

  

• When you attempt to export a package it fails and the following error is seen in the logs:

  java.lang.NullPointerException: Cannot invoke "java.security.cert.X509Certificate.getIssuerX500Principal()" because "c" is null
  at ch.dunes.crypto.KeyStoreManager.getPrincipal(KeyStoreManager.java:1070)
  at ch.dunes.crypto.KeyStoreManager.getSelfName(KeyStoreManager.java:804)
  at ch.dunes.model.pkg.impexp.PackageFileManager2.createMetaInfEntry(PackageFileManager2.java:585)
  at ch.dunes.model.pkg.impexp.PackageFileManager2.writePackage(PackageFileManager2.java:172)
  at com.vmware.o11n.service.impl.PackageImportServiceImpl.getExportDataForPackage(PackageImportServiceImpl.java:265)

Environment

• VCF Operations Orchestrator  9.0.x
• VCF Operations Orchestrator  9.1.0
• VCF Automation 9.0.x
• VCF Automation 9.1.0

Cause

This issue occurs due to a missing or corrupted package signing certificate within the Orchestrator internal keystore. When the backend service attempts to sign the newly created package, it fails to retrieve the certificate, resulting in a NullPointerException and generating the 500 Internal Server Error.

Servlet.service() for servlet [restServlet] threw exception
java.lang.NullPointerException: Cannot invoke "java.security.cert.X509Certificate.getIssuerX500Principal()" because the return value of "ch.dunes.model.client.IVSOFactoryClient.getSelfCertificate()" is null
    at com.vmware.o11n.web.packages.PackageController.lambda$createPackage$5(PackageController.java:293)

Resolution

This issue is under review with Broadcom Engineering. Subscribe to this knowledge article to get updates on this issue.

Workaround

To resolve this issue, you must recreate the corrupted keystore and generate a new package signing certificate using the built-in Orchestrator workflows.

1. Log in to the VCF Operations Orchestrator UI.
2. Navigate to Workflows > Library > Configuration > Keystores.
3. Run the Delete a keystore workflow.
4. In the workflow parameters, select the Dunes keystore and submit the run.
5. Navigate to Workflows > Library > Configuration.
6. Run the Generate Package Signing Certificate workflow.
7. Populate the Common name parameter. Leave all other parameters at their default values and submit the run.
8. Verify that packages can now be created and exported successfully.