Shin_Coldfire
Contributor
Contributor

Upgrading vCloud Director

Jump to solution

Greetings!

I have a soon to be production environment with vCloud Director 10.0 and NSX-v, vSphere 6.7. After a local webinar about new things in vCloud Director 10.1 I thought of upgrade to version 10.1 and NSX-T before I will ship this infrastructure to production use. Firstly, I've tried to upgrade my vCloud cell, then NSX. I've tried to follow this guide​ , but instead of local download I've used remote repo. Update successfully downloaded and installed. Upgraded DB without any errors, but after reboot, my updated vCloud Director can't connect to vSphere, that was already registered and worked in previous version. I reverted to a snapshot, checked, that old version is working without any issues and tried to upgrade again without any success.

Is upgrading to this version broken or it is well-known behavior of an upgrade process? Is my only option here is migration to a new cell?

Tags (1)
1 Solution

Accepted Solutions
paluszekd
VMware Employee
VMware Employee

Hello,

What was the errors you were seeing as it relates to failed connections to vSphere? Note that SSL management changed and if you are using self-signed certs for vSphere/NSX, you must re-accept these certs post-10.1 upgrade. I wrote about this new behavior here: https://www.paluszek.com/wp/2020/04/10/upgrading-to-vmware-cloud-director-10-1-ssl-management-change...

-Daniel

View solution in original post

2 Replies
paluszekd
VMware Employee
VMware Employee

Hello,

What was the errors you were seeing as it relates to failed connections to vSphere? Note that SSL management changed and if you are using self-signed certs for vSphere/NSX, you must re-accept these certs post-10.1 upgrade. I wrote about this new behavior here: https://www.paluszek.com/wp/2020/04/10/upgrading-to-vmware-cloud-director-10-1-ssl-management-change...

-Daniel

Shin_Coldfire
Contributor
Contributor

Hello, Daniel!

I want to thank you for a quick reply to my question. Your propose to simply re-enter credentials for vSphere and accept self-signed certificates worked. Never even thought about trying this simple solution. Thought it was some sort of a DB upgrade problem. Thank you very much!

p.s. Another great blog goes to my "favorites" tab Smiley Happy

0 Kudos