Red Hat Bugzilla – Bug 1260776
Error is displayed in the beginning of the deploy: "nodes with no profile that will not be used"
Last modified: 2016-04-25 23:45:59 EDT
Description of problem:
When deploying the overcloud we see:
WARNING: rdomanager_oscplugin.v1.overcloud_deploy.DeployOvercloud There are 6 ironic nodes with no profile that will not be used: c6974ddb-c02a-42b2-9beb-916d4dfcb187, b6a19a80-2e49-46c8-ad5a-97c3b46ea066, 51690ab8-9919-458c-a611-d5fff3ef6eec, 0c27d250-9a9a-4813-8e26-c43b073f9e4c, ab90f72f-ff12-4721-b625-6c6067518d31, dfc78417-bce9-4731-b314-3d2ad0d39f2e
ERROR: rdomanager_oscplugin.v1.overcloud_deploy.DeployOvercloud Configuration has 1 warnings, fix them before proceeding.
Despite the error which suggests that all nodes will be excluded from the deployment, the end deployment proceeds to a successful finish.
Version-Release number of selected component (if applicable):
poodle from 2015-09-05.2
Was reproduced twice in a virtualized setup and once on a BM setup
Steps to Reproduce:
1. I deployed with: openstack overcloud deploy --templates --control-scale 3 --compute-scale 1 --ceph-storage-scale 1 --ntp-server 10.5.26.10
After the error (which appears to be false?) deployment succeeds
Hey Udi, as I guessed it is coming from the rdomanager plugin (I didn't
have it in my setup - git blame says landed like 7 days ago)...
so the relevant code is . I don't know why it is happening, but
the warning is logged as a predeploy_warning. Since we are by default
setting validation_warnings_fatal to False, the deploy proceeds (it may
not be an actual problem with the nodes, or could be a sync. issue
(In reply to Udi from comment #3)
> From Marios:
> Hey Udi, as I guessed it is coming from the rdomanager plugin (I didn't
> have it in my setup - git blame says landed like 7 days ago)...
> so the relevant code is . I don't know why it is happening, but
> the warning is logged as a predeploy_warning. Since we are by default
> setting validation_warnings_fatal to False, the deploy proceeds (it may
> not be an actual problem with the nodes, or could be a sync. issue
Hi, I've made a patch to prevent this warning from showing when you don't specify flavors (as Udi did). See https://review.openstack.org/221940 for the upstream patch.
Reproduced on my setup too , deployment has failed on my side .
Installing all nodes on a single baremetal.
Here is the automation job:
Could you please suggest a workaround ?
The error here isn't what caused your deploy failure - this is just a validation check that isn't totally relevant for the virt use case. I've posted the patches to run the validation only when it's going to be useful, so you can ignore that error for now.
*** Bug 1264471 has been marked as a duplicate of this bug. ***
This change is now merged upstream, awaiting downstream review.
Downstream change is now merged, this will be included in the next build
Verified in: python-tripleoclient-0.0.11-5.el7ost.noarch (final beta puddle 2015-11-19.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.
has the following note that should be removed:
If using custom NIC templates from Red Hat OpenStack Platform 7, add the ManagementSubnetIp parameter to the parameters section of your NIC templates. For example:
ManagementIpSubnet: # Only populated when including environments/network-management.yaml
description: IP address/subnet on the management network
The ManagmentIpSubnet is already in the all of the OPS-d v8 nic-config files in /usr/share/openstack-tripleo-heat-template/network/config/*/* files - no need to add it again.