failure on Creation not helpful
Bug #1400527 reported by
Amit Gandhi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Poppy |
Fix Released
|
Medium
|
Amit Gandhi | ||
Bug Description
when creating a new service, sometimes a failure can occur at the provider level, or somewhere in Poppy.
Currently, the only indication of a failure is the status field on a GET request.
It would be helpful to be able to identify why a creation failed so that corrective action can be taken.
| Changed in poppy: | |
| assignee: | nobody → Amit Gandhi (amit-gandhi) |
| Changed in poppy: | |
| status: | New → In Progress |
Revision history for this message
| Amit Gandhi (amit-gandhi) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to poppy (master) | #2 |
| Changed in poppy: | |
| status: | In Progress → Fix Committed |
| Changed in poppy: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
a new error list will be returned with the service
"errors": []
if there are errors (because the service failed), it will appear similar to below with a list of messages:
"errors": [
"message": "FastlyError: An error occurred while connecting to the fastly API, please try your request again. (Name 'www.google.com' already taken for customer '6t78y9ueijo')"
]