Comment 1 for bug 1427772

I got to the end of the referenced thread <http://lists.openstack.org/pipermail/openstack-dev/2015-February/057090.html> and was none the wiser on what the chosen outcome was for this. There were several options bounced back and forth but nothing that seemed to win consensus. The options appeared to be:

* do nothing, let the targeted compute node fail when force_host is set if the host can't accept
    * except that apparently some claims can't be validated on-node
* pass the hosts listed as forced into the filters without changing the filters
* pass the hosts listed as forced into the filters but only run those filters which are deemed required when doing a force
* make a new command that is like force but means "force with filtering"
* but wait, forcing is antithetical to "cloud"; end users should not know or care about where stuff ends up as long as it is good enough, let's get rid of the force command

From what I can tell the sentence in the description beginning "Second reason..." suggests that "pass the hosts listed as forced into the filters without changing the filters" is the change that resolves the presenting problems with the smallest surface area of a change to the system.

So the question becomes: does the second reason matter?

If not we should mark this as incomplete, or invalid, or not a bug and get it off the radar.