Bug 1031786 - Error messages do not include enough information
Summary: Error messages do not include enough information
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack
Version: 4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 4.0
Assignee: Ivan Chavero
QA Contact: Nir Magnezi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-18 18:33 UTC by Ben Nemec
Modified: 2013-12-20 00:37 UTC (History)
7 users (show)

Fixed In Version: openstack-packstack-2013.2.1-0.19.dev935.el6ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-20 00:37:08 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 57010 0 None None None Never
Red Hat Product Errata RHEA-2013:1859 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2013-12-21 00:01:48 UTC

Description Ben Nemec 2013-11-18 18:33:06 UTC
Description of problem: Error reporting from remote scripts leaves something to be desired.


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


How reproducible: Always


Steps to Reproduce:
1. Attempt to use packstack on a system where ssh password authentication is disabled and root ssh keys are not configured.

Actual results: A failed install with no useful information about what is wrong.  For example:

ERROR : Failed to run remote script:

Note that by default there is also nothing in the log file to indicate what is wrong.


Expected results: An error message that includes the relevant failure, in the case above that would be:

ERROR : Failed to run remote script:
Warning: Permanently added '192.168.0.14' (RSA) to the list of known hosts.
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).


Additional info: The problem seems to be that when a command fails, only stdout is included in the error message.  Because this is a failure state, we should expect the useful information to be in stderr (though I think including stdout as well is probably a good idea).

I'm planning to propose a change that will address this shortly.

Comment 2 Ben Nemec 2013-11-18 19:17:43 UTC
Proposed fix: https://review.openstack.org/#/c/57010/

Comment 3 Ivan Chavero 2013-11-25 16:21:49 UTC
Proposed fix accepted.

Comment 8 errata-xmlrpc 2013-12-20 00:37:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2013-1859.html


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