Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1448103

Summary:	[RFE] Make introspection more reliable and improve the process for retrying failed nodes
Product:	Red Hat OpenStack	Reporter:	Dougal Matthews <dmatthew>
Component:	openstack-tripleo-common	Assignee:	Dougal Matthews <dmatthew>
Status:	CLOSED CURRENTRELEASE	QA Contact:	mlammon
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	11.0 (Ocata)	CC:	jjoyce, mburns, ohochman, rbrady, slinaber
Target Milestone:	z4	Keywords:	FutureFeature, TestOnly, Triaged, ZStream
Target Release:	11.0 (Ocata)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-common-6.1.1-1.el7ost	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-13 16:48:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.