bbb14264cb
There is a particular scenario when creating a new Manila share, whether through creating a new share or managing an existing one, where if no share type was explicitly specified and no default share type was configured the error message would not substitute the share type ID into the exception message. This is because, in this case, there was no share type ID to substitute into the string. This patch creates a new exception for explicitly handling the case where there is no default share type and no share type is explicitly given. It gives an appropriate error message about there not being a default share type and that there was no share type explicitly given as well as what would need to be done to remedy the situation. Change-Id: I068b55d4b77dc24b53fe93d870bb84e1aef661a5 Closes-Bug: #1700346
6 lines
168 B
YAML
6 lines
168 B
YAML
---
|
|
fixes:
|
|
- A new exception will be thrown when a default share type was not
|
|
configured and no other share type was specified on any sort of
|
|
share creation.
|