trove not supporting multiple regions
Bug #1361328 reported by
David Lyle
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| trove-dashboard |
Triaged
|
Low
|
David Lyle | ||
Bug Description
refactor of trove code in Horizon broke multi-region support.
| Changed in horizon: | |
| importance: | Undecided → High |
| assignee: | nobody → David Lyle (david-lyle) |
| milestone: | none → juno-3 |
| tags: | added: trov |
| tags: |
added: trove removed: trov |
Revision history for this message
| David Lyle (david-lyle) wrote | #1 |
| Changed in horizon: | |
| importance: | High → Low |
| Changed in horizon: | |
| status: | New → Triaged |
| Changed in horizon: | |
| milestone: | juno-3 → juno-rc1 |
| Changed in horizon: | |
| milestone: | juno-rc1 → kilo-1 |
| Changed in horizon: | |
| milestone: | kilo-1 → kilo-2 |
| Changed in horizon: | |
| milestone: | kilo-2 → next |
| affects: | horizon → trove-dashboard |
| Changed in trove-dashboard: | |
| milestone: | next → none |
To post a comment you must log in.
Ok, talked to trove folks. Trove doesn't really support multi-region the way I thought and has a little internal cleanup to do. This is not a bug in horizon, per say.
But right now we get a 500 error if trove throws and EndpointAmbiguity exception. That we could handle more cleanly. Making this a low.
Set up is have two nova endpoints in different regions and don't have the os_region_name field configured in the trove conf file (currently the default in devstack).