Description of problem: `default-node-count` validation fails if a user do `validation run` following the document. There are sections in the document `Installing and managing Red Hat OpenStack Platform with director`[1] of OSP17.1 in the following order: 11.2. Provisioning bare metal overcloud nodes 11.3.5. Validating your overcloud configuration 11.3.6. Creating your overcloud The section "11.3.5. Validating your overcloud configuration" mentions `validation run --group pre-deployment`. On the other hand, the `pre-deployment` group has the validation `default-node-count`. As far as I checked /usr/share/ansible/roles/default_node_count/tasks/main.yml, `default-node-count` expects that the provisioning state is `available`. However, as I wrote in the above, before a user run `validation run --group pre-deployment` by following "11.3.5. Validating your overcloud configuration", the provisioning state is already `active`. It is because the node provisioning is completed in "11.2. Provisioning bare metal overcloud nodes". Is it possible to fix this? [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.1/html-single/installing_and_managing_red_hat_openstack_platform_with_director/index#proc_validating-your-overcloud-configuration_ironic_provisioning
Hi all, I have updated the documentation with a workaround for the issue above. You can see the updates to the documentation here: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.1/html-single/installing_and_managing_red_hat_openstack_platform_with_director/index#proc_validating-your-overcloud-configuration_ironic_provisioning If you have any questions or require any further information, please let me know, Kid regards, Gareth
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days