[Ocata] nova.api.openstack Caught error: Could not determine a suitable URL for the plugin
I ran yum update
and now any request to the nova api fails with nova.api.openstack [-] Caught error: Could not determine a suitable URL for the plugin
. I can get the token from keystone
but when I use it to lookup hypervisors or a server it results in error.
List of updated packages and versions:
---> Package openstack-cinder.noarch 1:10.0.1-1.el7 will be updated
---> Package openstack-cinder.noarch 1:10.0.5-1.el7 will be an update
---> Package openstack-dashboard.noarch 1:11.0.1-2.el7 will be updated
---> Package openstack-dashboard.noarch 1:11.0.3-1.el7 will be an update
---> Package openstack-heat-api.noarch 1:8.0.1-1.el7 will be updated
---> Package openstack-heat-api.noarch 1:8.0.4-1.el7 will be an update
---> Package openstack-heat-api-cfn.noarch 1:8.0.1-1.el7 will be updated
---> Package openstack-heat-api-cfn.noarch 1:8.0.4-1.el7 will be an update
---> Package openstack-heat-common.noarch 1:8.0.1-1.el7 will be updated
---> Package openstack-heat-common.noarch 1:8.0.4-1.el7 will be an update
---> Package openstack-heat-engine.noarch 1:8.0.1-1.el7 will be updated
---> Package openstack-heat-engine.noarch 1:8.0.4-1.el7 will be an update
---> Package openstack-keystone.noarch 1:11.0.0-1.el7 will be updated
---> Package openstack-keystone.noarch 1:11.0.3-1.el7 will be an update
---> Package openstack-magnum-api.noarch 0:4.1.0-2.el7 will be updated
---> Package openstack-magnum-api.noarch 0:4.1.3-1.el7 will be an update
---> Package openstack-magnum-common.noarch 0:4.1.0-2.el7 will be updated
---> Package openstack-magnum-common.noarch 0:4.1.3-1.el7 will be an update
---> Package openstack-magnum-conductor.noarch 0:4.1.0-2.el7 will be updated
---> Package openstack-magnum-conductor.noarch 0:4.1.3-1.el7 will be an update
---> Package openstack-neutron.noarch 1:10.0.1-1.el7 will be updated
---> Package openstack-neutron.noarch 1:10.0.3-1.el7 will be an update
---> Package openstack-neutron-common.noarch 1:10.0.1-1.el7 will be updated
---> Package openstack-neutron-common.noarch 1:10.0.3-1.el7 will be an update
---> Package openstack-neutron-fwaas.noarch 1:10.0.1-1.el7 will be updated
---> Package openstack-neutron-fwaas.noarch 1:10.1.0-1.el7 will be an update
---> Package openstack-neutron-ml2.noarch 1:10.0.1-1.el7 will be updated
---> Package openstack-neutron-ml2.noarch 1:10.0.3-1.el7 will be an update
---> Package openstack-neutron-openvswitch.noarch 1:10.0.1-1.el7 will be updated
---> Package openstack-neutron-openvswitch.noarch 1:10.0.3-1.el7 will be an update
---> Package openstack-nova-api.noarch 1:15.0.3-2.el7 will be updated
---> Package openstack-nova-api.noarch 1:15.0.7-1.el7 will be an update
---> Package openstack-nova-common.noarch 1:15.0.3-2.el7 will be updated
---> Package openstack-nova-common.noarch 1:15.0.7-1.el7 will be an update
---> Package openstack-nova-conductor.noarch 1:15.0.3-2.el7 will be updated
---> Package openstack-nova-conductor.noarch 1:15.0.7-1.el7 will be an update
---> Package openstack-nova-console.noarch 1:15.0.3-2.el7 will be updated
---> Package openstack-nova-console.noarch 1:15.0.7-1.el7 will be an update
---> Package openstack-nova-novncproxy.noarch 1:15.0.3-2 ...
Nova uses these settings from the config file to access Keystone:
Are they correct? Can you try to obtain a token using the settings under [keystone_authtoken]?
Yes, I can get a token just fine.
Just for grins I added
/v3
toauth_uri
andauth_url
, then I started getting[SSL: CERTIFICATE_VERIFY_FAILED]
errors. I then addedcafile
, cert errors are gone but now it's getting an even more generic error. I've updated the post.