unable to stop starting jobs in stop status

[Fabrizio Vanni]

This is a freezer-api bug:
when a job is in a stop condition and a start has been requested it's status is still "stop" (and it stays sto untile the scheduler acknowledges the start request)

In that state, a stop request won't be accepted and the job event remains "start"

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/305958
Committed: https://git.openstack.org/cgit/openstack/freezer-api/commit/?id=bb5ba827eff2e3a8b8a32860e883be8de60ec58b
Submitter: Jenkins
Branch: master

commit bb5ba827eff2e3a8b8a32860e883be8de60ec58b
Author: Fabrizio Vanni <email address hidden>
Date: Thu Apr 14 15:00:28 2016 +0100

    fix job-stop request not accepted

    A job whose status is "stop" and event is "start" can now be correctly
    stopped. Its status will remain "stop" and its event set to "stop"

    Client are actually free to issue any start/stop request,
    the responsibility of detecting if the action request
    makes sense is on the scheduler

    Change-Id: I82da538840d67cbaed06a54a6c71e2bf75a174de
    Closes-Bug: #1570401

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/341410
Committed: https://git.openstack.org/cgit/openstack/freezer-api/commit/?id=17938d5b00fcf441fed95cf041357af4b7860c19
Submitter: Jenkins
Branch: stable/mitaka

commit 17938d5b00fcf441fed95cf041357af4b7860c19
Author: Fabrizio Vanni <email address hidden>
Date: Thu Apr 14 15:00:28 2016 +0100

    fix job-stop request not accepted

    A job whose status is "stop" and event is "start" can now be correctly
    stopped. Its status will remain "stop" and its event set to "stop"

    Client are actually free to issue any start/stop request,
    the responsibility of detecting if the action request
    makes sense is on the scheduler

    Cherry-pick from https://review.openstack.org/#/c/305958

    Change-Id: I82da538840d67cbaed06a54a6c71e2bf75a174de
    Closes-Bug: #1570401
    (cherry picked from commit bb5ba827eff2e3a8b8a32860e883be8de60ec58b)

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/freezer-api 3.0.0.0b2 development milestone.