OpenStack DBaaS (Trove)

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

Bug #1395523 reported by Denis M.
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Fix Released
High
Dariusz Krol
OpenStack DBaaS (Trove) ongoing

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.

Victoria Martinez de la Cruz (vkmc)
Changed in trove:
assignee: nobody → Victoria Martínez de la Cruz (vkmc)
Nikhil Manchanda (slicknik)
Changed in trove:
status: New → Confirmed
status: Confirmed → Triaged
Revision history for this message
Amrith Kumar (amrith) wrote :

vkmc, any updates on this bug?

Changed in trove:
importance: Medium → High
milestone: none → newton-1
Victoria Martinez de la Cruz (vkmc)
Changed in trove:
assignee: Victoria Martinez de la Cruz (vkmc) → nobody
Amrith Kumar (amrith)
Changed in trove:
milestone: newton-1 → ongoing
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (master)

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

Changed in trove:
assignee: nobody → Dariusz Krol (d.krol)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove (master)

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
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/trove 10.0.0.0rc1

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  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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