'This version of vCenter Server does not support Deploy OVF Template' error during OVF deployment after VCSA 6.5.x upgrade

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• OVF deployment fails after upgrading to vCenter Server Appliance 6.5 GA or 6.5.0a/EP01.
• OVF deployment fails after upgrading to vCenter Server Appliance 6.5 U1 onwards.

This version of vCenter Server does not support Deploy OVF Template using this version of vSphere Web Client. To Deploy OVF Template, login with version 6.5.0.0 of vSphere Web Client.

• In the vSphere Client (HTML 5 client), the Deploy OVF template option is grayed out.
   
• Running the service-control --status vmware-content-library command shows the Content Library service as not running.

Environment

VMware vCenter Server Appliance 6.7.x
VMware vSphere 6.7.x
VMware vCenter Server Appliance 6.5.x
VMware vSphere 6.5.x

Cause

• If this error occurs before upgrading VCSA 6.5 U1 version:

The cause would be due to an inconsistency in the SSO token signer certificate for environments upgraded from 5.1 or earlier.

• If this error occurs after upgrading to VCSA 6.5 U1 version:

The cause would be due to the ts-config.properties file is deployed with the noreplace option. With this option, the ts-config.properties will no longer be overwritten, instead it is saved with the extension .rpmnew.

 

This issue can happen for two reasons:

• The file had parameters added by a user in the past.
• During a major upgrade where a migration of the properties file is performed. A major upgrade path would be 6.0.x to 6.5.x to 6.5u1.

Resolution

When the error occurs upgrading VCSA to 6.5 GA or 6.5.0a version:
This issue is resolved in VMware vCenter Server Appliance 6.5 b.


When the error occurs after upgrading to VCSA 6.5 U1 version:
This issue is resolved in VMware vCenter Server 6.5 Update 1d.

Workaround:

Workaround for the error 'This version of vCenter Server does not support Deploy OVF Template':

When the error occurs upgrading VCSA to 6.5 GA or 6.5.0a version:

            To work around this issue, deploy OVF files using the command line.

 

When the error occurs after upgrading to VCSA 6.5 U1 version:

1. Connect to the vCenter Server Appliance with an SSH session and root credentials.
    
2. Run this command to enable access the Bash shell:
   
   shell.set --enabled true
    
3. Type shell and press Enter.
    
4. Navigate to /etc/vmware-content-library/config/ with this command:
   
   cd /etc/vmware-content-library/config/
    
5. Create a backup of the ts-config.properties and ts-config.properties.rpmnew file with these commands:
   
   cp ts-config.properties ts-config.properties.orig
   
   cp ts-config.properties.rpmnew ts-config.properties.rpmnew.orig
    
6. Rename ts-config.properties.rpmnew to ts-config.properties.
   
   mv ts-config.properties.rpmnew ts-config.properties
    
7. Restart the Content Library service:
   
   service-control --stop vmware-content-library;service-control --start vmware-content-library
    
8. Refresh the vSphere Web Client browser Window.

Note:-  Please contact Technical support if the file "ts-config.properties.rpmnew" is missing or not found.