rhel-osp-director: Configuration errors resulting from tagging nodes with profiles should prevent the deployment from starting. Environment: instack-undercloud-2.2.5-1.el7ost.noarch openstack-ironic-inspector-2.2.4-3.el7ost.noarch openstack-ironic-conductor-4.2.2-4.el7ost.noarch python-ironic-inspector-client-1.2.0-6.el7ost.noarch openstack-ironic-common-4.2.2-4.el7ost.noarch python-ironicclient-0.8.1-1.el7ost.noarch openstack-ironic-api-4.2.2-4.el7ost.noarch Steps to reproduce: 1. Deploy undercloud. 2. Assign profiles to nodes using this procedure: http://tripleo.org/advanced_deployment/profile_matching.html#examples-of-introspection-rules 3. Start a deployment with mispelling some profile name Result: 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 1 of 2 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 1 nodes with profile ceph-storage won't be used for deployment now Configuration has 2 errors, fix them before proceeding. Ignoring these errors is likely to lead to a failed deploy. Configuration has 1 warnings, fix them before proceeding. Deploying templates in the directory /usr/share/openstack-tripleo-heat-templates Expected result: The deployment shouldn't start.
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
*** Bug 1330333 has been marked as a duplicate of this bug. ***
Hi! I was testing OSP 10 the other day, and the error were actually fatal. Fixed?
*** Bug 1263792 has been marked as a duplicate of this bug. ***
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://rhn.redhat.com/errata/RHEA-2016-2948.html