How to extend the time allowed for overcloud create

hphelion

asked 2014-10-15 15:06:55 -0500

James Thompson
41 ●1 ●2 ●7

updated 2014-10-17 15:00:27 -0500

smaffulli
6981 ●38 ●68 ●102 http://maffulli.net/

I'm trying to install a 5 node baremetal HelionCE. The servers I'm using have a lot of RAM and some unused HBAs resulting in a long POST / boot time. After removing some HBAs to speedup the boot time 3 of the 5 nodes booted before hp_ced_installer.sh exited...

QUESTION: HOW can I increase the time allowed for the Overcloud creation ??

*+--------------------------------------+------------+--------------------+----------------------+
| id                                   | stack_name | stack_status       | creation_time        |
+--------------------------------------+------------+--------------------+----------------------+
| a87a40bf-4053-401e-9f2f-d3f2461a618d | overcloud  | CREATE_IN_PROGRESS | 2014-10-14T18:31:57Z |
+--------------------------------------+------------+--------------------+----------------------+
++ echo 'Waiting for the overcloud stack to be ready'
Waiting for the overcloud stack to be ready
+++ date
++ echo 'HP: Tue Oct 14 18:16:09 UTC 2014 this could take up to 30 or more minutes'
HP: Tue Oct 14 18:16:09 UTC 2014 this could take up to 30 or more minutes
++ wait_for_stack_ready 720 10 overcloud
Command output matched '(CREATE|UPDATE)_FAILED'. Exiting...*

edit retag flag offensive close merge delete

add a comment

1

answered 2014-12-03 12:53:55 -0500

James Thompson
41 ●1 ●2 ●7

I was able to successfully install the newer 1.4 version of Helion CE by changing my baremetal.csv file to have all identical mem/cpu/storage numbers ( my systems are not all the same).

edit flag offensive delete link

Comments

this is suggested by one of the release notes for 1.4

James Thompson ( 2014-12-03 12:54:35 -0500 )edit

add a comment

0

answered 2014-12-03 20:08:02 -0500

echiu
236 ●1 ●3 ●8

updated 2014-12-03 20:10:32 -0500

In tripleo/tripleo-incubator/scripts/hp_ced_overcloud.sh, you can adjust wait time in the following lines, depending on whether you are using ESX or not. Adjust the time parameters in the wait_for function, which is set to 30 minutes by default.

## #. _`Wait for Nova Compute`
##    ::
if [ "${OVERCLOUD_CLOUD_TYPE}" != "ESX" ] ; then
    wait_for 30 10 nova service-list --binary nova-compute 2\>/dev/null \| grep 'enabled.*\ up\ '
fi
### --end

## #. Wait for L2 Agent On Nova Compute
##    ::
# openvswitch agent will not run on ESX proxy compute. Check only on KVM compute node
if [ "${OVERCLOUD_CLOUD_TYPE}" != "ESX" ] ; then
    wait_for 30 10 neutron agent-list -f csv -c alive -c agent_type -c host \| grep "\":-).*Open vSwitch agent.*-novacompute\"" #nodocs
    ## wait_for 30 10 neutron agent-list -f csv -c alive -c agent_type -c host \| grep "\":-).*Open vSwitch agent.*overcloud-novacompute\""
fi
### --end

edit flag offensive delete link

add a comment

How to extend the time allowed for overcloud create

2 answers

Comments

Your Answer

Get to know Ask OpenStack

Question Tools

Stats

Related questions

Feedback About This Page

OpenStack

Community

Documentation

Branding & Legal

How to extend the time allowed for overcloud create edit

2 answers

Comments

Your Answer

Get to know Ask OpenStack

Question Tools

Stats

Related questions

Feedback About This Page

OpenStack

Community

Documentation

Branding & Legal

How to extend the time allowed for overcloud create