register-nodes error message hides the source of conflict.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
os-cloud-config |
Triaged
|
Medium
|
Ghe Rivero |
Bug Description
From a recent run:
2014-10-17 01:37:07 - requests.
2014-10-17 01:37:15 - ironicclient.
2014-10-17 01:37:22 - ironicclient.
2014-10-17 01:37:27 - root - ERROR - Unexpected error during command execution
Traceback (most recent call last):
File "/home/
blocking=True)
File "/home/
blocking=
File "/home/
raise ironicexp.
Conflict: Conflict (HTTP 409)
I have no idea what caused this Conflict.
Running again with --debug shows more detail:
2014-10-17 03:32:38 - ironicclient.
2014-10-17 03:32:38 - os_cloud_
2014-10-17 03:32:43 - root - ERROR - Unexpected error during command execution
Traceback (most recent call last):
File "/home/
blocking=True)
File "/home/
blocking=
File "/home/
raise ironicexp.
Conflict: Conflict (HTTP 409)
So now I know that a node was locked. That information should not require --debug to be displayed - I think that's pretty basic information that should be in the default output.
Looking a few lines earlier, I see a detailed error message:
NodeLocked: Node 0e9f8b6c-
This tells me which node is locked, and why. This information should be in the default error output rather than just "Conflict"
Changed in os-cloud-config: | |
assignee: | nobody → Ghe Rivero (ghe.rivero) |
status: | New → Triaged |
importance: | Undecided → Medium |