On Mon, Jul 13, 2015 at 07:56:36AM +0300, Eduard Matei wrote: > Hi, > > Forgot to mention, indeed we configured extra_specs: volume_backend_name. > The problem is that a volume of this type can get scheduled on a node where > c-vol is not configured with this backend. > > F.e.: I have 3 storage nodes (c-vol) and two have the driver configured, > the third one doesn't have it; when i try to create a volume of this type, > sometimes the c-vol on third node gets the call, and it fails because the > driver is not configured. > > Maybe we didn't configure something properly, i tried looking at c-sch but > i can't figure out why the third node got chosen. > > Thanks, > > Eduard
> __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Hi, You wouldn't happen to have the same hostname on all those 3 nodes, right? I mean, if all your storage nodes are running with something like localhost.localdomain, then the Scheduler (or the API node for that matter) won't be able to properly address them individually. Cheers, Gorka. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
