This is not a duplicate bug, since it's talking about freeing up the resources on the source host after a migration, not claiming resources on the destination.
This is not a duplicate bug, since it's talking about freeing up the resources on the source host after a migration, not claiming resources on the destination.