Bug 1321646

Summary:	[RFE] Clean up the 'openstack overcloud deploy' command output
Product:	Red Hat OpenStack	Reporter:	Marius Cornea <mcornea>
Component:	rhosp-director	Assignee:	Ana Krivokapic <akrivoka>
Status:	CLOSED WONTFIX	QA Contact:	Ola Pavlenko <opavlenk>
Severity:	medium	Docs Contact:
Priority:	low
Version:	8.0 (Liberty)	CC:	beth.white, dbecker, jcoufal, mburns, morazi, rhel-osp-director-maint
Target Milestone:	---	Keywords:	FutureFeature, Triaged, UserExperience
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	NeedsAllocation
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-13 16:05:58 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:

Description Marius Cornea 2016-03-28 18:23:17 UTC

Description of problem:
Currently there are a lot of '[0]: SIGNAL_COMPLETE  Unknown' messages in the 'openstack overcloud deploy' output which don't provide meaningful information about the deployment progress. Can we have those messages filtered?   

There are also some redundant messages in the output:

[overcloud-VipDeployment-ta25v33dfkoz]: UPDATE_COMPLETE  Stack UPDATE completed successfully
[overcloud-ObjectStorageAllNodesValidationDeployment-n5zuo32zvrhr]: CREATE_IN_PROGRESS  Stack CREATE started
[overcloud-ObjectStorageAllNodesValidationDeployment-n5zuo32zvrhr]: CREATE_COMPLETE  Stack CREATE completed successfully
[overcloud-ObjectStorageAllNodesValidationDeployment-n5zuo32zvrhr]: UPDATE_IN_PROGRESS  Stack UPDATE started

For instance, if the stack status is CREATE_IN_PROGRESS then I don't think the 'Stack CREATE started' is needed.

Comment 2 Mike Burns 2016-04-07 21:36:02 UTC

This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.