Im trying to deploy VIO 1.0.2 and after the Management server has powered on I don't get the icon in the web client even after I logout and log back in. Ive followed the release note instructions and navigated to https://[VMware Integrated OpenStack Manager Service IP Address]:8443/register-plugin/login.jsp but when I click the fix button I get a HTTP Status 500 - 400 Bad Request error (see attached for more detail). Does anybody know why this might be happening?
Hi,
This error is common if the DNS is not properly configured int he OMS server. Also sometimes the FQDN in the vCenter SSL certificate doesn’t match the VC FQDN itself.
Verify that DNS is configured in the management server and try to regenerate the SSL certificate for the vCenter, if you are using vCSA that’s pretty simple to do from the management portal via https://vc_ip:5480
Best Regards,
Karol
Can you log back in as administrator@vsphere.local and see if the icon has appeared?
It appeared when I logged back in but couldn't connect to the management server. Ive now removed everything and currently trying to reinstall the manager so hopefully when complete it will work.
I can get the icon to appear now but when I click on the icon its not connected to the management server. When I try to connect to the management sever I get the following error:
Connection failed! Please check whether the SSO has been enabled from the Openstack Management server log at:/installer.log
Any help would be grateful?
Hi,
This error is common if the DNS is not properly configured int he OMS server. Also sometimes the FQDN in the vCenter SSL certificate doesn’t match the VC FQDN itself.
Verify that DNS is configured in the management server and try to regenerate the SSL certificate for the vCenter, if you are using vCSA that’s pretty simple to do from the management portal via https://vc_ip:5480
Best Regards,
Karol
To be better identify the problem, Please log into management server and run "viogetlogs" Then please upload the log file.
Thanks KarolSte it was a DNS problem which I have now resolved and all is working fine now.