Hello all, has anyone else encountered this?
once upgrade to 10.2.2 is complete, I am greeted with:
here we see catalog sync is indeed broken:
It's certainty certificate related, however, all is working across my sites prior to upgrade.
I managed to fix this for anyone who is interested.
my NSX V Manager, checking SSL Certificates, I noticed that the Common Name (CN) was not a full fqdn, I just had a hostname in there.
added full fqdn, re-generated certs, then re-connected my VC in Cloud / vCenter Server Instances
..issue is fixed. I am now fully upgraded to latest verison.
Hi,
Have you imported and trusted certificates after the upgrade?
/opt/vmware/vcloud-director/bin/cell-management-tool trust-infra-certs --vsphere --unattended
Try to see if it fix your issues.
hey, thanks for the suggestion, yes I did try this, certs imported as expected from cli, but UI issue remained.
I'm going to try this again next week and will collect more data
Hey,
Do you have an update here?
We have the same issue at the moment. We are Subscribed to the bitnami catalog?
Hi,
sorry no, I have not had time to troubleshoot this further, I rolled back to 10.1
I suspect an underlying issue with my certs / config.
I managed to fix this for anyone who is interested.
my NSX V Manager, checking SSL Certificates, I noticed that the Common Name (CN) was not a full fqdn, I just had a hostname in there.
added full fqdn, re-generated certs, then re-connected my VC in Cloud / vCenter Server Instances
..issue is fixed. I am now fully upgraded to latest verison.
Good that you find it.
Honestly, I did that some issue some time ago, I cant remember the error, but it was a problem in the cert Common Name.