Generic error messages in Solum when trove is down

Bug #1398517 reported by Dimitry Ushakov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Solum
New
Undecided
Unassigned

Bug Description

Whenever Trove is non responsive, Solum is unusable and throws back HTTP 500 errors for most requests. We should have better error representation to our end users.

As a complement to this issue, we also have a single point of failure that's outside of our control (Trove) for something as simple as data storage. We should have a backup/redundant storage that would allow us to service requests even if downstream services are temporarily unavailable.

Tags: solum-infra
Revision history for this message
Adrian Otto (aotto) wrote :

Dimitry, are you referring to the Trove used for storing the Solum database, or Trove used as part of a Heat orchestration?

Changed in solum:
status: New → Incomplete
Revision history for this message
Devdatta Kulkarni (devdatta-kulkarni) wrote :

Dimitry is referring to Solum's control plane database.

Changed in solum:
status: Incomplete → New
tags: added: solum-infra
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.