volumev1 aggregation fails
Bug #1646520 reported by
Wjdan Alharthi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mix and Match (mixmatch) |
Fix Released
|
Undecided
|
Kristi Nikolla | ||
Bug Description
When a request to /volumes is made, the proxy aggregates the volumes. However, it needs more information about the volumes than /volumes provides. So we instead issue the call to /volumes/detail to get the extra information we need, use it to aggregate, remove the extra information (cleanup), and report to the user.
The current setup in the aggregation step works with volume v2 only and not volume v1.
| Changed in mixmatch: | |
| assignee: | nobody → Wjdan Alharthi (walharth) |
| Changed in mixmatch: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to mixmatch (master) | #1 |
| Changed in mixmatch: | |
| assignee: | Wjdan Alharthi (walharth) → Kristi Nikolla (knikolla) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to mixmatch (master) | #2 |
| Changed in mixmatch: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/