Bug #787
Allow exception info to propagate when allocating a VNC console in the API fails
| Status: | Closed | Start date: | 07/08/2011 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | Vangelis Koukis | % Done: | 0% |
|
| Category: | Cyclades API | Spent time: | - | |
| Target version: | v0.5.1 |
Description
The API implementation should allow exceptions to propagate when allocating a VNC console fails.
Catching the exception and throwing a generic ServiceUnavailable() fault hinders debugging.
This needs input from [verigak].
Associated revisions
Remove RAPI GetInstanceConsole() call
Remove RAPI GetInstanceConsole() call, because it returns a
potentially unusable endpoint based on cluster-wide vnc_bind_address,
usually 0.0.0.0 or 127.0.0.1. Until this is fixed on the Ganeti side,
we construct a console info reply based on the primary node and network
port as reported by RAPI GetInstance(), fixes #783.
Allow exceptions to propagate when talking to the VNC authentication
proxy, fixes #787.
History
#1 Updated by Vangelis Koukis almost 13 years ago
- Status changed from New to Closed
- Assignee changed from Giorgos Verigakis to Vangelis Koukis
Merged into master, 71099804f6, closing ticket.