Hi Chuan!
Thanks for raising this bug report. We discussed this at a weekly IRC meeting and have a couple of questions:
1) Can you please share the migration command you used? we're interested to know if you're performing a nondisruptive share migration; where we believe manila is cleaning up the share servers immediately: https://github.com/openstack/manila/blob/3b9cfe126fbb5d83febe6f9f8747be3c4ce787c4/manila/share/manager.py#L5823-L5839 Otherwise, it could take some time for the share server deletion routine to pick up the share server and delete it.
2) How do you plan to rollback? If a nondisruptive migration occurred, we expect that the storage system doesn't have the share server in the original host; and a rollback would really be a different migration operation.
Hi Chuan!
Thanks for raising this bug report. We discussed this at a weekly IRC meeting and have a couple of questions:
1) Can you please share the migration command you used? we're interested to know if you're performing a nondisruptive share migration; where we believe manila is cleaning up the share servers immediately: https:/ /github. com/openstack/ manila/ blob/3b9cfe126f bb5d83febe6f9f8 747be3c4ce787c4 /manila/ share/manager. py#L5823- L5839
Otherwise, it could take some time for the share server deletion routine to pick up the share server and delete it.
2) How do you plan to rollback? If a nondisruptive migration occurred, we expect that the storage system doesn't have the share server in the original host; and a rollback would really be a different migration operation.