Pulp 3 migration abort fails with 409
A migration cancel task was found to fail with a 409 conflict, which failed the migration in Katello, resulting in losing track of the migration task. After talking with the Pulp team, it looks like the 409 pops up if you try to cancel a Pulp task that is already complete. We should investigate this. I think we may be hitting the 409 when we loop through the tasks in the task group. If it really is the issue, we can simply handle the 409 and skip sending the cancel request.
According to the Pulp team, a 409 will be returned if you try to cancel a task that is failed, completed, skipped or, canceled.