Bug 1330801

Summary:	error when attempting to deploy on fewer than tagged nodes
Product:	Red Hat OpenStack	Reporter:	Dan Yocum <dyocum>
Component:	python-openstackclient	Assignee:	Jason E. Rist <jrist>
Status:	CLOSED NOTABUG	QA Contact:	Shai Revivo <srevivo>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0 (Liberty)	CC:	apevec, beth.white, dyocum, lhh, skinjo, srevivo
Target Milestone:	async	Keywords:	Triaged, ZStream
Target Release:	8.0 (Liberty)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-31 15:12:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dan Yocum 2016-04-27 01:24:38 UTC

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.

Comment 2 Shinobu KINJO 2017-01-24 01:26:30 UTC

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.

Comment 3 Dan Yocum 2017-02-06 16:12:16 UTC

If that's the case, then that should be properly documented.  Is it?

Comment 4 Shinobu KINJO 2017-02-06 18:11:33 UTC

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.

Comment 5 Beth White 2017-08-31 15:12:15 UTC

Closing based on above comments. Documentation being constantly worked on to improve.