Ask Your Question
0

Failure retrieving ROUTER_GW_IP

asked 2015-12-03 13:54:52 -0600

Josh67 gravatar image

updated 2015-12-04 01:37:19 -0600

dbaxps gravatar image

I happened to see this error msg "Failure retrieving ROUTER_GW_IP", every time I run the ./stack.sh ... Google search doesn't turn up any useful help. Also another guy asked this question in this forum before, but the provided answer has nothing to do with this issue. I'm using the following local.conf snippets:

[[local|localrc]]
HOST_IP=192.168.0.120
FIXED_RANGE="10.0.0.0/24"
FLOATING_RANGE="192.168.0.128/25"
Q_FLOATING_ALLOCATION_POOL=start=192.168.0.129,end=192.1268.0.254
PUBLIC_NETWORK_GATEWAY="192.168.0.1"

# Multihost devstack
MULTI_HOST=True

# Logging
DEBUG=True
VERBOSE=True
DEST=/opt/stack
LOGFILE=$DEST/logs/stack.sh.log
SCREEN_LOGDIR=$DEST/logs/screen

SYSLOG=False
LOG_COLOR=False
LOGDAYS=7

# Main Services
# Keystone
ENABLED_SERVICES=key
# Nova
ENABLED_SERVICES+=,n-api,n-cpu,n-cond,n-sch,n-novnc,n-crt,n-cauth
# Glance ser
ENABLED_SERVICES+=,g-api,g-reg
# Cinder
ENABLED_SERVICES+=,c-sch,c-api,c-vol
# Dashboard
ENABLED_SERVICES+=,horizon
# Heat
ENABLED_SERVICES+=,heat,h-api,h-api-cfn,h-api-cw,h-eng
# Additional services
ENABLED_SERVICES+=,rabbit,mysql
ENABLED_SERVICES+=,s-proxy,s-object,s-container,s-account

# Ceilometer
enable_service ceilometer-acentral
enable_service ceilometer-collector
enable_service ceilometer-alarm-singleton
enable_service ceilometer-alarm-notifier
enable_service ceilometer-alarm-evaluator
enable_service ceilometer-api
CEILOMETER_BACKEND=mongodb

# Enable Swift
enable_service s-proxy s-object s-container s-account
SWIFT_HASH=66a3d6b56c1f479c8b4e70ab5c2000f5
SWIFT_REPLICAS=1
SWIFT_DATA_DIR=$DEST/data

# Neutron
enable_service neutron
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
#enable_service q-fwaas
#enable_service q-lbaas
#enable_service q-vpn
enable_service q-meta
#enable_service q-metering

# Allow tenants to create vlans
ENABLE_TENANT_VLANS=True
ENABLE_TENANT_TUNNELS=False
TENANT_VLAN_RANGE=1100:2999
edit retag flag offensive close merge delete

Comments

This entry Q_FLOATING_ALLOCATION_POOL=start=192.168.0.129,end=192.1268.0.254
It could be a reason.

dbaxps gravatar imagedbaxps ( 2015-12-04 01:39:25 -0600 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-08-03 10:01:12 -0600

jckreddy gravatar image
Yes Rightly said bdaxps That is the root cause 

typo error(space) between start and end ips 
Q_FLOATING_ALLOCATION_POOL="start=10.130.98.190, end=10.130.98.197" 
corrected to below one 
Q_FLOATING_ALLOCATION_POOL="start=10.130.98.190,end=10.130.98.197"
now working
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-12-03 13:54:52 -0600

Seen: 231 times

Last updated: Aug 03 '16