Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1288544 - [introspection] introspection return code incorrect
[introspection] introspection return code incorrect
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient (Show other bugs)
8.0 (Liberty)
All All
high Severity high
: ga
: 8.0 (Liberty)
Assigned To: Dmitry Tantsur
Raviv Bar-Tal
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-04 09:32 EST by Joe Talerico
Modified: 2016-04-07 17:43 EDT (History)
7 users (show)

See Also:
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.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-04-07 17:43:35 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:0604 normal SHIPPED_LIVE Red Hat OpenStack Platform 8 director Enhancement Advisory 2016-04-07 21:03:56 EDT

  None (edit)
Description Joe Talerico 2015-12-04 09:32:22 EST
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 08:56:09 EST
Sorry, I didn't realize the fix is already available
Comment 5 errata-xmlrpc 2016-04-07 17:43:35 EDT
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.