c458dff54c
For the moment if we create share from snapshot from first attempt we get share created from scratch, not from snapshot. This bug appered after merge of [1] to manila and usage of 2.6+ microversion in Manila UI. The reason why [1] had influence is in changed share view that became incompatible with 'choices' in UI that depend on share type names. So, start using correct field 'share_type_name', that will set default value for share type omitting the need to set it manually all the time, it also will trigger correct snapshot ID selection for request. Also, fix logic for second+ attempt, where we were using different set of data after failed attempt to submit request. [1] I082bdac82c981adf733c709472ce1b9e26d5650b Change-Id: I4b5a04ed16d8e579ad816e84ad907ddd97e13ac1 Closes-Bug: #1685657
6 lines
200 B
YAML
6 lines
200 B
YAML
---
|
|
fixes:
|
|
- Fixed form of share creation from snapshot. Before it was losing
|
|
source snapshot ID in request and was creating share from scratch instead
|
|
of expected snapshot-sourced variant.
|