Bug 1645645

Summary:	Spine-Leaf Guide - node-data.yaml example incorrect
Product:	Red Hat OpenStack	Reporter:	Jeremy <jmelvin>
Component:	documentation	Assignee:	RHOS Documentation Team <rhos-docs>
Status:	CLOSED DUPLICATE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	dmacpher
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-01 14:36:27 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:
Embargoed:

Description Jeremy 2018-11-02 17:45:40 UTC

Description of problem:

During our deployment of OSP 13 (Spine-Leaf) we ran into an issue where only 1 of each node type would deploy during the OverCloud deployment.  It ended up being that the documentation for the node-data.yaml in the Spine-Leaf guide (Chapter 2.3, step#4) is incorrect.  The node type count lines should not include the word "Overcloud." However in  the Director installation guide it has it correct.  Please update the Spine-Leaf guide with the correct values.

Documented Incorrectly (2.4/#4) -  https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/spine_leaf_networking/configuring-the-undercloud#creating-flavors-for-spine-leaf-nodes

Documented Correctly (6.7/#2) - https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/director_installation_and_usage/chap-configuring_basic_overcloud_requirements_with_the_cli_tools#sect-Creating_an_Environment_File_that_Defines_Node_Counts_and_Flavors

Comment 2 Dan Macpherson 2019-10-01 14:36:27 UTC


*** This bug has been marked as a duplicate of bug 1649813 ***