Targeted deployments still try to "find a new host" if nova-compute encounters an error

[Guangya Liu (Jay Lau)]

Scenario:
-----------
1. Have RetryFilter enabled in nova.conf filter options
2. Use --availability_zone :host-foo boot parameter when booting a VM
3. host-foo encountered a problem during its nova-compute spawn (e.g., storage problem)
4. nova-scheduler, because an exception was encountered, tries to find a new host

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/41588

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/41588
Committed: http://github.com/openstack/nova/commit/90620a27e0831345864f574256b30bac1ced5843
Submitter: Jenkins
Branch: master

commit 90620a27e0831345864f574256b30bac1ced5843
Author: Jay Lau <email address hidden>
Date: Tue Aug 13 11:06:56 2013 +0800

    Disable retry filter with force_hosts or force_nodes

    If customer deploy a VM with force_hosts or force_nodes options,
    then there is no need to retry even if retry filter was enabled.

    Fix bug 1211597

    Change-Id: I2948f48b5c4982cc29899b76889d7d8f0db47449