List objects in file bank is not correct

Bug #1802815 reported by jiaopengju
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Karbor
Fix Released
Undecided
jiaopengju

Bug Description

When using file bank as the backend, execute 'karbor checkpoint-list <provider-id> --plan_id <plan-id>', it will fail with “Checkpoint by-plan/1fd687b8-7c85-4936-9fe7-33ad2f923d54/79b35e99a6a541b3bcede40f590d6878/2018-11-09 could not be found. (HTTP 404) (Request-ID: req-db22a616-b3e2-4efc-9d4a-7ed70e2435ad)”

It is because that, in the bank, checkpoints by plan are stored as "<bank_path>/karbor/indices/by-plan/<plan_id>/<project_id>/<date>/<checkpoint>", the file bank plugin only list the <date> level, not include the checkpoint level.

This should be fixed.

jiaopengju (pj-jiao)
Changed in karbor:
assignee: nobody → jiaopengju (pj-jiao)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to karbor (master)

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

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

Reviewed: https://review.openstack.org/617224
Committed: https://git.openstack.org/cgit/openstack/karbor/commit/?id=fd17f48547553dbef3d36a79cb3670b61cdeb817
Submitter: Zuul
Branch: master

commit fd17f48547553dbef3d36a79cb3670b61cdeb817
Author: jiaopengju <email address hidden>
Date: Mon Nov 12 12:43:29 2018 +0800

    Fix listing checkpoints by plan error with FS bank

    When listing checkpoints by plan with using FS bank,
    it will fail with 'could not be found' error. The reason
    is, in the bank, checkpoints by plan are stored as
    "<bank_path>/karbor/indices/by-plan/<plan_id>/<project_id>
    /<date>/<checkpoint>", but the file bank plugin only list
    the <date> level, not include the checkpoint level. This
    patch will fix it.

    Closes-Bug: #1802815

    Change-Id: I8c1356269277647490925e0181e2cd1dfca1fa4e

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

This issue was fixed in the openstack/karbor 1.2.0 release.

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

Other bug subscribers

Remote bug watches

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