Comment 2 for bug 1203152

Moving this to 'Invalid'. I am not able to recreate the problem reported by the user and they also are unable to recreate the problem.

I am able to get one thread of execution in the _ensure_vdisk_no_fc_mappings function. It will sit there waiting for the vdisk to be in a state where it can be deleted. I can start a second delete request and it will get to the _ensure_vdisk_no_fc_mappings function and also wait.

So, given that, if the problem does still exist I don't think that the problem could be at this point in the code. Can always reopen if the problem reappears.