Wrong examples in "Getting started with TripleO-Quickstart in tripleo-quickstart"

Bug #1734209 reported by Victoria Martinez de la Cruz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Invalid
Medium
Unassigned

Bug Description

Examples for different sections are wrong. It performs the same operation for the different actions.

Precisely,

Install the Undercloud
Prepare for the Overcloud deployment
Deploy the Overcloud
Validate the Overcloud is functional

Have the same example,

"bash quickstart.sh -R master --no-clone --tags all --nodes config/nodes/1ctlr_1comp.yml -I --teardown none -p quickstart-extras-undercloud.yml $VIRTHOST"

Which is correct for the "Install the undercloud" section but not for the other sections.

-----------------------------------
Release: 2.1.1.dev251 on None
SHA: 47159a5447ad72ecb4e1003d5790e3315f513a63
Source: https://git.openstack.org/cgit/openstack/tripleo-quickstart/tree/doc/source/getting-started.rst
URL: https://docs.openstack.org/tripleo-quickstart/latest/getting-started.html

Changed in tripleo:
importance: Undecided → Medium
milestone: none → queens-3
Revision history for this message
yatin (yatinkarel) wrote :

I can see that there are different examples for each section and so each example performs different operation:-
Section:- Prepare the TripleO Overcloud for deployment:-
Example:- bash quickstart.sh -R master --no-clone --tags all --nodes config/nodes/1ctlr_1comp.yml -I --teardown none -p quickstart-extras-overcloud-prep.yml $VIRTHOST

Section:- Deploy the TripleO Overcloud:-
Example:- bash quickstart.sh -R master --no-clone --tags all --nodes config/nodes/1ctlr_1comp.yml -I --teardown none -p quickstart-extras-overcloud.yml $VIRTHOST

So, -p <playbook> is different in each section.

I have tried these steps and everything worked.

Did i got something wrong?

Changed in tripleo:
status: New → Triaged
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.