SSPI upgrade precheck failed with HTTP Error: 500 Server Error

Products

• VMware vDefend Firewall with Advanced Threat Prevention

Issue/Introduction

During an SSPI upgrade, the VSphere Upload Content Library step fails with a 500 Internal Server Error. The SSPI platform API cannot upload the SSP node OVA to the vCenter Content Library because the Content Library storage backing is unavailable or in an unknown state in vCenter.

Ex: 

[VSphere Upload Content Library] Error occurred while executing the upgrade step. An unexpected exception occurred: HTTPError: 500 Server Error: Internal Server Error for url: http://localhost:8080/sspi/platform/1/ova/create-template

 Secop logs :

node/ova/ssp-node-5.1.1.0.0.25224334.ova", "error": "400 Bad Request: {\"type\":\"com.vmware.vapi.std.errors.invalid_argument\",\"value\":{\"error_type\":\"INVALID_ARGUMENT\",\"messages\":[{\"args\":[\"Datastore:datastore-xxxx:xxxxxx-660b-42f7-92e6-xxxxx\",<SKIP>"default_message\":\"The provided storage backing Datastore:Datastore:datastore-xxxx:xxxxxx-660b-42f7-92e6-xxxxx

 

In vcenter content lib summary: 

 

Environment

SSP5.x

 

Cause

Due to a vCenter issue, the Content Library becomes unavailable or enters an unknown state. This causes the SSPI upgrade preflight check for the Content Library to fail, blocking the OVA upload step. The Content Library storage backing reference stored in vCenter becomes stale or inaccessible — commonly triggered by:

• vCenter migration or redeployment
• Datastore disconnection or removal
• vCenter certificate replacement
• Content Library datastore running out of space
• Partial or failed previous upgrade leaving the Content Library in a bad state

 

Resolution

• Rename the current content libary 
  • ex: content-lib.old
• Create the new content lib with exactly the same name. 
  
  • All setting are default 
  • datastore should be the original location that content lib was installed. 
• Restart the SSPI upgrade.