I had a working VIO version 2.0 and tried to upgrade it to 2.5.
The upgrade steps succeeded through the viocli dbverify step.
I went to provision the new VIO deployment and vCenter can no longer connect to the OMS instance. I can ssh to it just fine, I've shutdown and restarted the vApp that contains OMS to no avail. I tried to connect directly to the web interface at https://<OMS_server>:8443/VIO and logged in with the vCenter credentials as it suggests and I get the resulting http 500 error page from the servlet.
Anyone else get this and get past it?
Thanks.
I meant run that on the controller node.. not the management server
Hi Sidharth,
Any chance you've had a look at this since last week? I'm still trying to determine why cinder won't successfully launch.
Thanks!
raflax, try this on both controllers:
edit the file:
/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.py
add the line:
@_retry_on_deadlock
just before:
"def service_update(context, service_id, values): "
restart cinder services
I've tried what you've suggested and there is no difference. The logs still indicate the same failure. Any other ideas?