Bug 1288544 - [introspection] introspection return code incorrect
Summary: [introspection] introspection return code incorrect
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 8.0 (Liberty)
Hardware: All
OS: All
high
high
Target Milestone: ga
: 8.0 (Liberty)
Assignee: Dmitry Tantsur
QA Contact: Raviv Bar-Tal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-04 14:32 UTC by Joe Talerico
Modified: 2016-04-07 21:43 UTC (History)
7 users (show)

Fixed In Version: python-tripleoclient-0.1.1-2
Doc Type: Bug Fix
Doc Text:
Previously, bulk introspection only printed on-screen errors, but never returned a failure status code. This prevented introspection failures from being detected. This update changes the status code of errors to non-zero, which ensures that failed introspections can now be detected through their status codes.
Clone Of:
Environment:
Last Closed: 2016-04-07 21:43:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:0604 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 8 director Enhancement Advisory 2016-04-08 01:03:56 UTC

Description Joe Talerico 2015-12-04 14:32:22 UTC 
During Khaleesi a bulk introspection is ran to pull the node information. However if a failure occurs the error code is always returned as 0. For better error reporting, if a introspection fails (timeout/etc) return a proper status code.

Dmitry quickly pushed a patch for this: https://review.openstack.org/#/c/253476/
Comment 2 Dmitry Tantsur 2016-02-02 13:56:09 UTC 
Sorry, I didn't realize the fix is already available
Comment 5 errata-xmlrpc 2016-04-07 21:43:35 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.

https://rhn.redhat.com/errata/RHEA-2016-0604.html
Note You need to log in before you can comment on or make changes to this bug.