Yeah, so it looks to me that glance tries to determine the store from the URI itself, as it calls this with nothing more than the URI provided:
https://github.com/openstack/glance/blob/922e544ca2556994450e6972403ba4313318c5e0/glance/common/store_utils.py#L159-L178
Which, as Lee suggested, goes along with not having a parameter (that I know of either) to provide the store name in the location update.
That function can fail if the scheme map isn't working, which makes me wonder about your stores= config:
stores = glance.store.filesystem.Store, glance.store.http.Store,glance.store.rbd.Store
which is different from how it's specified in our job:
stores = file, http, rbd
Could that be related?
Yeah, so it looks to me that glance tries to determine the store from the URI itself, as it calls this with nothing more than the URI provided:
https:/ /github. com/openstack/ glance/ blob/922e544ca2 556994450e69724 03ba4313318c5e0 /glance/ common/ store_utils. py#L159- L178
Which, as Lee suggested, goes along with not having a parameter (that I know of either) to provide the store name in the location update.
That function can fail if the scheme map isn't working, which makes me wonder about your stores= config:
stores = glance. store.filesyste m.Store, glance. store.http. Store,glance. store.rbd. Store
which is different from how it's specified in our job:
stores = file, http, rbd
Could that be related?