Search the VMware Knowledge Base (KB)
View by Article ID

OVF deployment fails after upgrading to vCenter Server Appliance 6.5 U1 (2151085)

  • 49 Ratings

Symptoms

  • This issue is seen after upgrading to vSphere 6.5 Update 1.  If you see this error on a previous version, see OVF deployment fails after upgrading to vCenter Server Appliance 6.5 (2148007).

  • OVF deployment fails after upgrading to vCSA,you see error similar to:

    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.

Cause

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

This is a known issue seen with several upgrade paths to vSphere 6.5 Update 1. Not all upgrade paths are affected, VMware is investigating affected paths this article will be updated once confirmed.

Currently, there is no resolution.

To work around this issue:

  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.

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Action box.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 49 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 49 Ratings
Actions
KB: