OpenStack Backup/Restore and DR (Freezer)

unable to stop starting jobs in stop status

  1. Series mitaka
  2. Bug #1570401
Bug #1570401 reported by Fabrizio Vanni
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Backup/Restore and DR (Freezer)
Fix Released
Undecided
Unassigned
Mitaka
Fix Committed
Undecided
Domhnall Walsh

Bug Description

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"

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to freezer-api (master)

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

Changed in freezer:
status: New → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to freezer-api (stable/mitaka)

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)

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/freezer-api 3.0.0.0b2

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.