Bug 1369270

Summary: [RFE] OpenStack Director Deploy or Update Should Provide Details on Preview (Dry-Run)
Product: Red Hat OpenStack Reporter: Benjamin Schmaus <bschmaus>
Component: openstack-tripleo-heat-templatesAssignee: James Slagle <jslagle>
Status: CLOSED ERRATA QA Contact: Gurenko Alex <agurenko>
Severity: high Docs Contact:
Priority: medium    
Version: 8.0 (Liberty)CC: aschultz, athomas, dbecker, gkeegan, jcoufal, jjoyce, jslagle, jthomas, marjones, mburns, mcornea, morazi, rhel-osp-director-maint
Target Milestone: Upstream M2Keywords: FutureFeature, Triaged
Target Release: 14.0 (Rocky)Flags: marjones: needinfo? (jslagle)
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-9.0.0-0.20180710202746.d2994ca.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1665485 (view as bug list) Environment:
Last Closed: 2019-01-11 11:47:00 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:
Bug Depends On:    
Bug Blocks: 1615694, 1665485    

Description Benjamin Schmaus 2016-08-22 22:20:37 UTC
Description of problem: Customer would like to be able to preview a Director overcloud deploy and update without actually taking any actions but have the details of what would be executed and run and where in the environment.  One  would think the --dry-run option would do something like this but on a deploy we only see this:

[stack@ospvd ~]$ openstack overcloud deploy --templates --control-scale 1 --compute-scale 1  --ntp-server pool.ntp.org --neutron-network-type vxlan --neutron-tunnel-types vxlan  --dry-run --verbose
START with options: ['overcloud', 'deploy', '--templates', '--control-scale', '1', '--compute-scale', '1', '--ntp-server', 'pool.ntp.org', '--neutron-network-type', 'vxlan', '--neutron-tunnel-types', 'vxlan', '--dry-run', '--verbose']
command: overcloud deploy -> tripleoclient.v1.overcloud_deploy.DeployOvercloud
Using auth plugin: password
SUCCESS: No warnings or errors in deploy configuration, proceeding.
No stack found, will be doing a stack create
Validation Finished
END return value: 0



Version-Release number of selected component (if applicable): OSP8


How reproducible:
100%


Steps to Reproduce:
1.Run any deploy with the --dry-run --verbose options
2.
3.

Actual results:
[stack@ospvd ~]$ openstack overcloud deploy --templates --control-scale 1 --compute-scale 1  --ntp-server pool.ntp.org --neutron-network-type vxlan --neutron-tunnel-types vxlan  --dry-run --verbose
START with options: ['overcloud', 'deploy', '--templates', '--control-scale', '1', '--compute-scale', '1', '--ntp-server', 'pool.ntp.org', '--neutron-network-type', 'vxlan', '--neutron-tunnel-types', 'vxlan', '--dry-run', '--verbose']
command: overcloud deploy -> tripleoclient.v1.overcloud_deploy.DeployOvercloud
Using auth plugin: password
SUCCESS: No warnings or errors in deploy configuration, proceeding.
No stack found, will be doing a stack create
Validation Finished
END return value: 0



Expected results:
Customer would like to see detail on what is getting created, what hosts would be used to deploy and what steps would happen on those hosts.


Additional info:

Comment 6 Jaromir Coufal 2017-07-25 18:36:08 UTC
*** Bug 1465577 has been marked as a duplicate of this bug. ***

Comment 8 Jaromir Coufal 2017-08-17 15:34:36 UTC
After discussions with engineering team, this feature seems to be supportable with Ansible integration, which is coming in later releases, pushing this out of OSP13.

In the meantime there are feature to check Heat resources being creating, heat-template syntax and other validations which can be run prior to deployment (and its update).

Comment 18 Gurenko Alex 2018-11-28 14:32:18 UTC
Verified on puddle: 2018-11-21.2

Comment 21 errata-xmlrpc 2019-01-11 11:47:00 UTC
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://access.redhat.com/errata/RHEA-2019:0045