Bug 917734 - "Node execution failure (invalid exit code from node). If the problem persists please contact Red Hat support." message
Summary: "Node execution failure (invalid exit code from node). If the problem persist...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: OKD
Classification: Red Hat
Component: Pod
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Abhishek Gupta
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-04 16:31 UTC by Matt Reid
Modified: 2015-05-15 02:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-12 18:44:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
node execution failure message (31.26 KB, image/png)
2013-03-04 16:32 UTC, Matt Reid
no flags Details

Description Matt Reid 2013-03-04 16:31:43 UTC
Description of problem:
I was trying to spin up an app Thursday night and hit errors the first 4 times or so I went through the process. The error was "Node execution failure (invalid exit code from node). If the problem persists please contact Red Hat support."

As a user who has no idea what that means, my only choice was to keep trying and see if would eventually go through, since the messaging made it sound temporary.

It might be nice if that message was more actionable from a user's point of view, I'm seeing this message, what should I do about it? Should I just try again in 5 minutes? immediately? an hour? Can I try a different node somehow? Would a different app type go to a different node? If I back out and go through the process again, does that maybe get me on a different node?

If nothing else, it would be nice if when you told them to contact Red Hat support, if that was a link to information on how to contact support, instead of putting the onus on the user to go find out how they should report this failure they're seeing.

Version-Release number of selected component (if applicable):
current web

How reproducible:
happened several times trying to create new standard ruby on rails and django apps, after multiple tries, eventually the creation process was successful

Additional info:

Comment 1 Matt Reid 2013-03-04 16:32:22 UTC
Created attachment 705063 [details]
node execution failure message

Comment 2 Paul Morie 2013-03-04 18:32:04 UTC
This is meant to be a general catch-all message.  We'll work to improve the error message in the future.

Comment 3 manoj 2013-04-12 18:35:37 UTC
FutureFeature as we will create a story in the Broker storyboard

Comment 4 Abhishek Gupta 2013-04-12 18:44:00 UTC
A user story to track this has been created and added to the backlog.

https://trello.com/card/provide-granular-error-messages-for-node-execution-failure-during-mcollective-calls/50fc6a1d6ecd57e86a0075d1/43


Note You need to log in before you can comment on or make changes to this bug.