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:
*** Bug 1465577 has been marked as a duplicate of this bug. ***
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).
Verified on puddle: 2018-11-21.2
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days