This actually turned out to be a mis-configuration of the cinder v1 endpoint.
On Wednesday, July 13, 2016 at 2:11:33 PM UTC-5, Patrick Vinas wrote: > > Looking further into this, it appears that scalr is trying to use the v1 > cinder API, which was deprecated in Kilo, even though v2 and v3 of the API > are both available. Is there a configuration option somewhere to force > using v2? > > On Wednesday, July 13, 2016 at 12:24:16 PM UTC-5, Patrick Vinas wrote: >> >> When I try to launch a farm in my Openstack environment, no cinder >> volumes are created. >> >> Go to Sidebar->Openstack->Volumes, no volumes are listed - just an error: >> "Unable to load data (OpenStack error. Array)." >> >> There are no errors in the cinder logs on my Openstack controllers, and >> the following in the php-errors.log: >> PHP Fatal error: Uncaught exception >> 'Scalr\Service\OpenStack\Exception\RestClientException' with message >> 'OpenStack error. Array' in >> /opt/scalr-server/embedded/scalr/app/src/Scalr/Service/OpenStack/Exception/OpenStackResponseErrorFactory.php:25 >> >> Anyone have any suggestions? >> >> Running scalr community 5.11.22 >> > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
