Redundant initialization of swift client if we do not use swift storage

Bug #1705603 reported by jiaopengju on 2017-07-21
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Backup/Restore and DR (Freezer)
Undecided
jiaopengju

Bug Description

Currently, if we use 's3', 'local' or 'ssh' as storage type, freezer also do the initialization of swift client in the process of creating image, it seems not correct (The initialization requires the installation of swift). So this should be fixed.

jiaopengju (pj-jiao) on 2017-07-21
Changed in freezer:
assignee: nobody → jiaopengju (pj-jiao)
jiaopengju (pj-jiao) on 2017-07-21
description: updated
Changed in freezer:
status: New → In Progress

Reviewed: https://review.openstack.org/486115
Committed: https://git.openstack.org/cgit/openstack/freezer/commit/?id=55d6645b07f79c1e0d3dfd2c7c3972e374670667
Submitter: Jenkins
Branch: master

commit 55d6645b07f79c1e0d3dfd2c7c3972e374670667
Author: Pengju Jiao <email address hidden>
Date: Fri Jul 21 19:48:56 2017 +0800

    Remove redundant initialization of swift client

    When using ssh, local or s3 storage, freezer do not need do the
    initialization of swift client in the process of creating image.

    Change-Id: I5280d3e97bed7f2c488acc2ed6bd2befe1f21b88
    Closes-Bug: #1705603

Changed in freezer:
status: In Progress → Fix Released

This issue was fixed in the openstack/freezer 5.0.0.0b3 development milestone.

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

Other bug subscribers