if fix previous bug, this should be avoidable ? otherwise, delete a migration record should update compude node and without compute node this should raise some exception, so it's a work as designed behaviour?
if fix previous bug, this should be avoidable ?
otherwise, delete a migration record should update compude node and without compute node this should raise some exception, so it's a work as designed behaviour?