Description of problem: Attempting to follow the directions, here: https://access.redhat.com/documentation/en/red-hat-openstack-platform/version-8/director-installation-and-usage/#sect-Assign_Specific_Node_IDs doesn't work. Version-Release number of selected component (if applicable): [stack@ops2 ~]$ rpm -qa | grep 'ironic\|tripleo' | sort openstack-ironic-api-4.2.2-4.el7ost.noarch openstack-ironic-common-4.2.2-4.el7ost.noarch openstack-ironic-conductor-4.2.2-4.el7ost.noarch openstack-ironic-inspector-2.2.5-2.el7ost.noarch openstack-tripleo-0.0.7-1.el7ost.noarch openstack-tripleo-common-0.3.1-1.el7ost.noarch openstack-tripleo-heat-templates-0.8.14-7.el7ost.noarch openstack-tripleo-heat-templates-kilo-0.8.14-7.el7ost.noarch openstack-tripleo-image-elements-0.9.9-1.el7ost.noarch openstack-tripleo-puppet-elements-0.0.5-1.el7ost.noarch python-ironicclient-0.8.1-1.el7ost.noarch python-ironic-inspector-client-1.2.0-6.el7ost.noarch python-tripleoclient-0.3.4-2.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. update all nodes to have indexed profile names. 2. create scheduler_hints_env.yaml and include it in the openstack deploy overcloud 2. deploy overcloud 3. Actual results: Error: only 0 of 3 requested ironic nodes are tagged to profile control (for flavor control) Recommendation: tag more nodes using ironic node-update <NODE ID> replace properties/capabilities=profile:control,boot_option:local Error: only 0 of 1 requested ironic nodes are tagged to profile compute (for flavor compute) Recommendation: tag more nodes using ironic node-update <NODE ID> replace properties/capabilities=profile:compute,boot_option:local Error: only 0 of 4 requested ironic nodes are tagged to profile ceph-storage (for flavor ceph-storage) Recommendation: tag more nodes using ironic node-update <NODE ID> replace properties/capabilities=profile:ceph-storage,boot_option:local Configuration has 3 errors, fix them before proceeding. Ignoring these errors is likely to lead to a failed deploy. Expected results: success! Additional info:
Thanks for the ticket. The error does seem to come from the validation tools in OSP and also seems seems duplicated with https://bugzilla.redhat.com/show_bug.cgi?id=1318445 marking it as such. *** This bug has been marked as a duplicate of bug 1318445 ***