Resource name missing in stack create failed error

Bug #1339892 reported by Vijendar Komalla
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Triaged
Low
Kunal Rawtani

Bug Description

When a stack creation fails, the error message does not include the failed resource name.
For example, see the following error message/stack trace;
{"explanation": "The server could not comply with the request since it is either malformed or otherwise incorrect.", "code": 400, "error": {"message": "{u'Error': u'Interval must be larger than Timeout'}", "traceback": "Traceback (most recent call last):\n\n File \"/opt/stack/heat/heat/engine/service.py\", line 63, in wrapped\n return func(self, ctx, *args, **kwargs)\n\n File \"/opt/stack/heat/heat/engine/service.py\", line 568, in create_stack\n stack.validate()\n\n File \"/opt/stack/heat/heat/engine/parser.py\", line 428, in validate\n raise StackValidationFailed(message=result)\n\nStackValidationFailed: {'Error': 'Interval must be larger than Timeout'}\n", "type": "StackValidationFailed"}, "title": "Bad Request"}

Including resource name in the error message helps in identifying the problem.

Changed in heat:
assignee: nobody → Vijendar Komalla (vijendar-komalla)
status: New → In Progress
status: In Progress → New
Revision history for this message
Zane Bitter (zaneb) wrote :

Note, this is about stack validation, not stack creation. Errors during the actual creation of a stack are always reported in context.

Angus Salkeld (asalkeld)
Changed in heat:
importance: Undecided → Low
status: New → Triaged
Changed in heat:
assignee: Vijendar Komalla (vijendar-komalla) → zhaozhilong (zhaozhilong)
Changed in heat:
assignee: zhaozhilong (zhaozhilong) → nobody
Changed in heat:
assignee: nobody → Kunal Rawtani (rawtani-kunal)
Rico Lin (rico-lin)
Changed in heat:
milestone: none → no-priority-tag-bugs
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.