The same issue existed in Grizzly and was fixed to align with the scheduler behavior here: https://review.openstack.org/#/c/19369/ It probably broke when the migration path was moved from the scheduler to the conductor.
The same issue existed in Grizzly and was fixed to align with the scheduler behavior here: https:/ /review. openstack. org/#/c/ 19369/
It probably broke when the migration path was moved from the scheduler to the conductor.