af3513d2b0
While performing nondisruptive migrations, share servers can not change, because such thing will cause the migration to be disruptive, since share servers have different network allocations and it will cause the destination share to change its export locations. This change fixes an issue that allowed manila/the share driver to chose where a share instance is going to land in case of a nondisruptive migration. Now, when such migration is required, manila will automatically place the destination share instance in the same share server that the source instance is located at. Closes-Bug: #1920942 Change-Id: I16110ec46c25be65760b15d7fbed67cd005f3873
9 lines
283 B
YAML
9 lines
283 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Non-disruptive share migration will no longer choose a different
|
|
destination server even if limits of shares or gigabytes were exceeded in
|
|
the source.
|
|
For more details, please see
|
|
`bug #1920942 <https://bugs.launchpad.net/manila/+bug/1920942>`_.
|