Generic error messages in Solum when trove is down
Bug #1398517 reported by
Dimitry Ushakov
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.
Revision history for this message
| Adrian Otto (aotto) wrote | #1 |
| Changed in solum: | |
| status: | New → Incomplete |
Revision history for this message
| Devdatta Kulkarni (devdatta-kulkarni) wrote | #2 |
| Changed in solum: | |
| status: | Incomplete → New |
| tags: | added: solum-infra |
To post a comment you must log in.
Dimitry, are you referring to the Trove used for storing the Solum database, or Trove used as part of a Heat orchestration?