Replication setup silently fails if Swift as Remote Storage is not available

Bug #1395523 reported by Denis M. on 2014-11-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
High
Dariusz Krol

Bug Description

Per Storage strategy. There should be a validation step at an API service level that checks if remote storage is available.
For example, for Swift we should validate that it's available before trying to setup replication.

Also, there should explicit way to tell user actual reasons of replication failure.

Changed in trove:
assignee: nobody → Victoria Martínez de la Cruz (vkmc)
Changed in trove:
status: New → Confirmed
status: Confirmed → Triaged
Amrith Kumar (amrith) wrote :

vkmc, any updates on this bug?

Changed in trove:
importance: Medium → High
milestone: none → newton-1
Changed in trove:
assignee: Victoria Martinez de la Cruz (vkmc) → nobody
Amrith Kumar (amrith) on 2016-09-18
Changed in trove:
milestone: newton-1 → ongoing

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

Changed in trove:
assignee: nobody → Dariusz Krol (d.krol)
status: Triaged → In Progress

Reviewed: https://review.openstack.org/586528
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=4d358c8f5de4f7feda17053fb363be033146c9dc
Submitter: Zuul
Branch: master

commit 4d358c8f5de4f7feda17053fb363be033146c9dc
Author: Dariusz Krol <email address hidden>
Date: Fri Jul 27 14:18:28 2018 +0200

    Fix replication failure when Swift isn't available

      * add Swift token verification in create instance method in Trove API
        when slave_id is given
      * catch ConnectionError exception in verify_swift_auth_token
      * add Swift token verification to guestagent before backup and restore
      * add new exception representing Swift connection error
      * set missing fault information when replication snapshot fails
      * mock verify auth token method in replication and restore unit tests

    Closes-Bug: #1395523

    Change-Id: I6a21ba2ba890a82875f9b6dae3c6b93bc9fdb4b0
    Signed-off-by: Dariusz Krol <email address hidden>

Changed in trove:
status: In Progress → Fix Released

This issue was fixed in the openstack/trove 10.0.0.0rc1 release candidate.

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

Other bug subscribers