Bug 1321646 - [RFE] Clean up the 'openstack overcloud deploy' command output
Summary: [RFE] Clean up the 'openstack overcloud deploy' command output
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: Ana Krivokapic
QA Contact: Ola Pavlenko
URL:
Whiteboard: NeedsAllocation
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-28 18:23 UTC by Marius Cornea
Modified: 2018-03-13 16:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-13 16:05:58 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.