Availability zones v2 is not tested and used correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-cinderclient |
Fix Released
|
Undecided
|
Eugeniya Kudryashova |
Bug Description
Availability zones v1 and v2 duplicate each other. Tests for v2 zones actually duplicates tests for v1 zones (in import statemens also[1]), so v2 zones is not actually tested.
Availability zones v2 is not used in v2 client[2], this module have only one usage in shell v2[3]. This usage doesn't seems correct. We obtain zone using manager v1[4](because both v1 and v2 clients use v1 availability zones manager), but try to process it using v2 manager[5], this works only because this managers are equal.
[1]https:/
[2]https:/
[3]https:/
[4]https:/
[5]https:/
Changed in python-cinderclient: | |
assignee: | nobody → Eugeniya Kudryashova (ekudryashova) |
Changed in python-cinderclient: | |
milestone: | none → 1.3.1 |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/79703
Review: https:/