Some notable investigation -
1. Process stopped in disk migration stage itself
2. Stopped on 26% and then took that digit from backend and updated 26% in UI after cancellation which is best part
3. Instance not found when cancelled
4. Volume got properly cleaned
5. Port not found since it is canceled before this stage.
We are very happy with how it behaved for OSP. Thanks a lot for fixing this.
Tested on: 5.10.6.1.20190621202107_58f5bbc
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:1644