Bug #2952
Failing network operations set state despite API error return value
| Status: | Closed | Start date: | 10/19/2012 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | Kostas Papadimitriou | % Done: | 0% |
|
| Category: | Cyclades UI | Spent time: | - | |
| Target version: | 0.11.0 |
Description
To reproduce: try to destroy a private network with machines still connected to it.
The state turns to "Destroying..." although an API error value is returned to the user.
History
#1 Updated by Kostas Papadimitriou over 11 years ago
- Status changed from Assigned to Feedback
Cannot reproduce. Destroying private network (action which is prohibited unless UI_NETWORK_STRICT_DESTROY setting is set to False) returns "Machines are connected to network." API Error.
Testing on latest ui-0.11 branch
#2 Updated by Vangelis Koukis over 11 years ago
- Status changed from Feedback to Assigned
Hadn't made it clear enough: Yes, the API operation fails with exactly this API error, but then the private network is shown as "Destroying", even though the API request failed. One would expect the network to be changed to "Destroying..." only if the API request had been successful.
Didn't know about the setting, although [if the problem actually exists] it doesn't really matter: It should be reproducible by having DELETE /network/id requests fail unconditionally.
#3 Updated by Kostas Papadimitriou over 11 years ago
- Status changed from Assigned to Feedback
#4 Updated by Vangelis Koukis over 11 years ago
- Status changed from Feedback to Closed
Closing ticket.