Hide Forgot
Description of problem: I have 13 compute nodes. For testing, I only want to deploy on 1. Version-Release number of selected component (if applicable): python-openstackclient-1.7.2-1.el7ost.noarch How reproducible: every Steps to Reproduce: 1. have X number of compute nodes 2. Run: openstack overcloud deploy \ -t 120 \ --templates \ --control-scale 3 \ --compute-scale 1 \ --ceph-storage-scale 4 \ --control-flavor control \ --compute-flavor compute \ --ceph-storage-flavor ceph-storage \ --neutron-network-type vxlan \ --neutron-tunnel-types vxlan \ --ntp-server 10.5.26.10 \ --validation-errors-fatal \ --validation-warnings-fatal \ -e /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml \ -e ~/templates/network-environment.yaml \ -e ~/templates/storage-environment.yaml \ -e ~/templates/rhel-registration/environment-rhel-registration.yaml \ -e ~/templates/rhel-registration/rhel-registration-resource-registry.yaml \ -e ~/templates/timezone.yaml \ -e ~/templates/enable-tls.yaml \ -e ~/templates/cloudname.yaml \ -e ~/templates/inject-trust-anchor.yaml Actual results: 12 nodes with profile compute won't be used for deployment now Configuration has 1 warnings, fix them before proceeding. Expected results: success! Additional info: When I specify 13, then everything works fine.
The behaviour you have been facing is not bug. You may want to set maintenance mode to nodes which you are not going to deploy.
If that's the case, then that should be properly documented. Is it?
Yeah, it might make sense to document that. But in reality regarding to OSP, OpenStack, it's too *much* difficult to document whatever we find. It's because that the resource of documentation team is very limited. I've been still discussing this with documentation team (plus others) since last year about how we *could* improve ourselves by ourselves.
Closing based on above comments. Documentation being constantly worked on to improve.