Bug 1272740 - Failing to scale overcloud in RHEL-OSP 7.1
Summary: Failing to scale overcloud in RHEL-OSP 7.1
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 7.0 (Kilo)
Assignee: chris alfonso
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
: 1272741 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-18 11:32 UTC by Qasim Sarfraz
Modified: 2016-04-18 06:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-20 14:49:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Qasim Sarfraz 2015-10-18 11:32:44 UTC
Description of problem:
I am following the instructions in section 7.6 of official deployment guide. Following command is failing to to scale the overcloud:
$ openstack overcloud deploy --templates --compute-scale 2
After I execute this command controllers go into ERROR state.

Steps to Reproduce:
1- Create an overcloud with following command:
$  openstack overcloud deploy --templates --control-scale 3 --compute-scale 1 --control-flavor control --compute-flavor compute --ntp-server pool.ntp.org
2- Once the overcloud has been deployed use the following command to scale:
$ openstack overcloud deploy --templates --compute-scale 2

Actual results:
Failed deployment.

Expected results:
Overcloud should scale. In my case it should go from 1 compute nodes to 2 computes nodes.

Additional info:
If I use the following command to scale the overcloud it works:
openstack overcloud deploy --templates --control-scale 3 --compute-scale 2 --control-flavor control --compute-flavor compute --ntp-server pool.ntp.org

Is it a documentation bug? 
Also, I don't want to update the controller while scaling is there a way to do it?

Comment 2 Mike Burns 2015-10-18 13:08:25 UTC
*** Bug 1272741 has been marked as a duplicate of this bug. ***

Comment 3 chris alfonso 2015-10-19 16:07:45 UTC
You'll need to use the exact same deployment command on the second deployment, only changing the value of the compute scale for this to work.

Comment 4 chris alfonso 2015-10-19 16:08:17 UTC
Once you've done the above, will you let us know if you are still running into issues?

Comment 5 Qasim Sarfraz 2015-10-20 00:17:29 UTC
(In reply to chris alfonso from comment #4)
> Once you've done the above, will you let us know if you are still running
> into issues?

Using the exact same deployment command for the second time worked for me.

Comment 6 Mike Burns 2015-10-20 14:49:02 UTC
Thanks, closing this bug.  Please reopen if it reproduces


Note You need to log in before you can comment on or make changes to this bug.