Comment 11 for bug 1781710

Hmm, I see that before scheduling, conductor pulls the instance group from the DB again to refresh it's members list and it sets the policies on it again, but the filter is acting on the 'policy' field, so is it possible that we're just not setting the policy field properly during scheduling?

osboxes@osboxes:~/git/nova$ grep -R spec.instance_group.policies
nova/scheduler/utils.py: request_spec.instance_group.policies = group_info.policies