Relying on provider_id from database for SolidFire deletes is a bad idea
Bug #1494597 reported by
John Griffith
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
John Griffith |
Bug Description
After working on incorporating the use of provider_id fields in the SolidFire driver, I realized there's some flaws here. The main one being that the implementation currently in the driver doesn't account for things like a failed create.
populating provider-id fields in the db isn't harmful, but it's probably best not to rely on it. There are other/better ways to optimize lookups in our case.
Changed in cinder: | |
milestone: | none → liberty-rc1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | liberty-rc1 → 7.0.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/222484
Review: https:/