Errors in Cue should be propagated to the user
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cue |
New
|
Medium
|
Unassigned |
Bug Description
When a request is issued (ie to create a cluster), if the error happens in cue, the cluster goes to ERROR but the user does not know the cause of it. At least, the user should be returned a message, or an ID (that the user can use to track the error).
This was reproed when a cluster was created and nova failed to create the VM for cue due to not having enough IP available. Here is the error from cue-worker.
2015-10-21 18:21:10.446 32477 WARNING taskflow.
Traceback (most recent call last):
File "/opt/stack/
result = task.execute(
File "/opt/stack/
port = self.os_
File "/opt/stack/
ret = self.function(
File "/opt/stack/
return self.post(
File "/opt/stack/
headers=
File "/opt/stack/
self.
File "/opt/stack/
exception_
File "/opt/stack/
status_
The cluster went to ERROR but the user didnt know the cause. I had to look into the logs to find the issue.
Changed in cue: | |
importance: | Undecided → High |
importance: | High → Medium |
Reviewed: https:/ /review. openstack. org/244308 /git.openstack. org/cgit/ openstack/ cue/commit/ ?id=1be42880706 dd45d15686bc3ea beb58af546bfb0
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1be42880706dd45 d15686bc3eabeb5 8af546bfb0
Author: dagnello <email address hidden>
Date: Wed Nov 11 12:50:10 2015 -0800
Adding support for error details on cluster creation
Cue's current implementation does not provide any additional information cluster_ task now extracts failure flow details and forwards this
to the user related to why a cluster went into ERROR state during
cluster creation. This patch adds error_detail field in the
clusters table and exposes this field through the API. The
update_
information on cluster record update.
Partial-Bug: 1508730 1189585479b8d2c 1219a98cf40
(updates also required to Cue client and dashboard)
Closes-bug: 1516735
Change-Id: I440fec30bc3d05