Bug 2183451

Summary: [DDF] Overcloud deploy cannot be performed using the --config-download-only option before the stack is created
Product: Red Hat OpenStack Reporter: Direct Docs Feedback <ddf-bot>
Component: documentationAssignee: Irina <igallagh>
Status: CLOSED CURRENTRELEASE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 17.0 (Wallaby)CC: igallagh, joflynn, jpodivin, jslagle, rhayakaw, tasakura
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-02 15:55:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Direct Docs Feedback 2023-03-31 07:54:42 UTC
Since the resource by stack has not been created before deploying overcloud, it is assumed that `--config-download-only` cannot be executed at this time.

Reported by: rhn-support-tasakura

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.0/html/director_installation_and_usage/assembly_provisioning-and-deploying-your-overcloud#annotations:1e57a321-153e-4a87-b3fa-aa3d64d3c9bf

Comment 3 James Slagle 2023-05-18 11:34:04 UTC
In step 2 from https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.0/html-single/director_installation_and_usage/index#proc_validating-your-overcloud-configuration_ironic_provisioning,

replace --config-download-only with --stack-only.

Also remove the wording "plan". As there is no plan in 17. I would just call it "stack".

Comment 4 Jiri Podivin 2023-05-18 17:14:00 UTC
Regarding validations aspect. Always run validations with explicitly defined inventory file, if at all possible.
Otherwise you get the 'No host matched' error, because the runtime has no idea how to reach target machines.
The reasons col may be too large to see all results at once. In that case I would recommend changing output format, it is one of the CLI params,
and piping the result into a file. After that you can use UUIDs of individual validations to inspect their results in detail.