Cannot run cinder-volume with SolidFire driver in active/active
Bug #1179671 reported by
Mathieu Gagné
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
Mathieu Gagné | ||
Grizzly |
Fix Released
|
High
|
Mathieu Gagné |
Bug Description
When using SolidFire driver, cinder-volume cannot be run in active/active mode.
If the SolidFire account is created by the host "cinder01", we see this exception on the host "cinder02":
SfAccountNotFound: Unable to locate account cinder01-
The SolidFire account is created with a prefix based on the hostname of the host running cinder-volume. We should be able to disable or override the prefix with our own to be able to run in active/active mode.
Changed in cinder: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
importance: | Undecided → High |
tags: | added: grizzly-backport-potential |
Changed in cinder: | |
milestone: | havana-1 → 2013.2 |
tags: | removed: grizzly-backport-potential |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/29007
Review: https:/