Bug 1448103 - [RFE] Make introspection more reliable and improve the process for retrying failed nodes
Summary: [RFE] Make introspection more reliable and improve the process for retrying f...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: z4
: 11.0 (Ocata)
Assignee: Dougal Matthews
QA Contact: mlammon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-04 14:21 UTC by Dougal Matthews
Modified: 2017-12-13 16:48 UTC (History)
5 users (show)

Fixed In Version: openstack-tripleo-common-6.1.1-1.el7ost
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-13 16:48:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1669830 0 None None None 2017-05-04 14:22:13 UTC
OpenStack gerrit 439568 0 None None None 2017-05-04 14:22:50 UTC

Description Dougal Matthews 2017-05-04 14:21:30 UTC 
Introspection can cause problems at scale, this is due to two primary issues:

- Introspection is attempted for all nodes in one batch
- It is hard to retry failed nodes, without retrying everything


USER STORIES:

* As a cloud operator I want to introspect batches of nodes so the introspection service does not stall or fail
Comment 1 Dougal Matthews 2017-05-04 14:25:11 UTC 
USER STORIES:

* As a cloud operator I want introspection to automatically retry failed nodes and keep me informed about progress
Comment 3 Jon Schlueter 2017-11-15 01:58:42 UTC 
According to our records, this should be resolved by openstack-tripleo-common-6.1.1-1.el7ost.  This build is available now.
Comment 5 mlammon 2017-12-12 15:46:00 UTC 
I have not seen any issues in this area when introspecting nodes on BM environment and have seen introspection retry failed nodes. Moving to verified.
Note You need to log in before you can comment on or make changes to this bug.