glance_store

BadStoreConfiguration propagation on exact filesystem_store_datadirs duplicate

Bug #1428257 reported by Gorka Eguileor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
glance_store
Fix Released
Medium
Gorka Eguileor
glance_store 0.5.0
Kilo
Fix Released
Medium
Unassigned

Bug Description

With new BadStoreConfiguration propagation to the library user (as per bug #1422699) we don't want to propagate the exception (which will prevent glance from starting) when we have the exact same path and priority is used in 2 filesystem_store_datadirs on a filesystem backend; as there is no confusion on what the configuration intends.

If the same path is used but with 2 different priorities it should keep propagating BadStoreConfiguration exception as it is, since the library cannot know which priority is the right one.

Gorka Eguileor (gorka)
Changed in glance-store:
assignee: nobody → Gorka Eguileor (gorka)
status: New → In Progress
Revision history for this message
Nikhil Komawar (nikhil-komawar) wrote :

https://review.openstack.org/#/c/157013/

Changed in glance-store:
milestone: none → 0.5.0
importance: Undecided → Medium
Nikhil Komawar (nikhil-komawar)
Changed in glance-store:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.