OpenStack Backup/Restore and DR (Freezer)

Can't start failed job again in web-ui

Bug #1625189 reported by Ruslan Aliev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Backup/Restore and DR (Freezer)
Fix Released
Undecided
jiaopengju

Bug Description

Nothing happens if failed job started.

jiaopengju (pj-jiao)
Changed in freezer:
assignee: nobody → jiaopengju (pj-jiao)
status: New → In Progress
Revision history for this message
jiaopengju (pj-jiao) wrote :

It is because freezer-scheduler has filtered all the job with status 'completed'.
It is not very easy to modify the freezer-scheduler's search option, because freezer-api only support 'must' and 'must not' query of elasticsearch.

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

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

commit 655d803b449fe608b0fe6afc7781bce3582dff24
Author: Pengju Jiao <email address hidden>
Date: Wed May 17 17:20:12 2017 +0800

    Fix start failed job not working

    Currently, when we start a failed job, nothing will happen.
    It is because freezer-scheduler has filtered all the job with
    status 'completed'. This patch will fix it.

    Change-Id: I9ef420ba5dbf1e80582a6b0ab947646630a6b7fa
    Closes-Bug: #1625189

Changed in freezer:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/freezer-api 5.0.0.0b3

This issue was fixed in the openstack/freezer-api 5.0.0.0b3 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.