Ask Your Question
0

VIPs are not reachable after fule-based installation

asked 2016-01-11 05:13:37 -0600

ChrisHC gravatar image

hi,

i have a problem with fuel 7 - i installed a controller and 3 kvm's for a small test-environment. after installation (fuel says "successfully deployed") i cannot reach the vip's of f.e. horizon or auth-url. but i can reach the controllers ip's without a problem. all the services are up and running. i can access horzion through the management network, but not through the public one.

so the problem is, as the vip's are not available, i can't do anything on kvm (f.e. create an instance), as the kvm host is not able to reach the vip's and their services like glance, authentication, etc. etc. - > Unable to establish connection to http://192.168.x.x:5000/v2.0/tokens

does some having the same problem while installing openstack throuth fuel ? does anyone know this / a solution for this problem ?

i really appreciate your help ! thanks in advance, chris

edit retag flag offensive close merge delete

Comments

here some more information from the kvm's nova-all.log the last message is the most relevant one: nova.compute.manager [instance: <>] ConnectionRefused: Unable to establish connection to http://192.168.0.2:35357/v2.0/tokens

ChrisHC gravatar imageChrisHC ( 2016-01-11 05:35:57 -0600 )edit

Make sure, your keystone service is up and running. initctl list | grep keystone & netstat -ntlp | grep 35357

Bipin gravatar imageBipin ( 2016-01-12 00:02:28 -0600 )edit

please see below

ChrisHC gravatar imageChrisHC ( 2016-01-12 02:25:10 -0600 )edit

2 answers

Sort by ยป oldest newest most voted
0

answered 2016-01-12 02:30:40 -0600

ChrisHC gravatar image

updated 2016-01-12 02:36:00 -0600

hi bipin,

when i run both commands on the controller (not the kvm-host) i get this:

initctl list | grep keystone
keystone start/running, process 31334
netstat -ntlp | grep 35357
tcp6 0 0 :::35357 :::* LISTEN 7238/apache2
netstat -ntlp | grep 5000
tcp6 0 0 :::5000 :::* LISTEN 7238/apache2
-> has tcp6 something to say ? should it be tcp4 ?

when i run this one on the KVM-HOST: glance image-list
Unable to establish connection to http://192.168.0.2:5000/v2.0/tokens

but when i run the same thing on the CONTROLLER: glance image-list
+--------------------------------------+---------------+-------------+------------------+------------+--------+
| ID | Name | Disk Format | Container Format | Size | Status |
+--------------------------------------+---------------+-------------+------------------+------------+--------+
| e132215f-4164-4ea4-8c1e-d654541975ef | w2k8r2-cbinit | qcow2 | bare | 7458324480 | active |
+--------------------------------------+---------------+-------------+------------------+------------+--------+

so it seams that all the services on the controller are up and running.

what i saw is that f.e. i can "telnet <controller-vip> 80" on the CONTROLLER, but i CAN NOT "telnet <controller-ip> 80" on the KVM-HOST when i use the haproxy VIP. looks like all the VIPs are not accessable from outside the controller. when i change the .conf and environment variable for auth-url from the vip to the controllers ip it works ...

are there any other services that have to be in running-state on the controller ?:

initctl list | grep stop
mountall-net stop/waiting
passwd stop/waiting
rc stop/waiting
startpar-bridge stop/waiting
ureadahead-other stop/waiting
console-setup stop/waiting
hwclock-save stop/waiting
neutron-dhcp-agent stop/waiting
neutron-ovs-cleanup stop/waiting
plymouth-log stop/waiting
failsafe stop/waiting
mounted-var stop/waiting
nova-spicehtml5proxy stop/waiting
plymouth-shutdown stop/waiting
plymouth stop/waiting
udev-fallback-graphics stop/waiting
umm-console stop/waiting
control-alt-delete stop/waiting
hwclock stop/waiting
mounted-proc stop/waiting
umm stop/waiting
setvtrgb stop/waiting
shutdown stop/waiting
heat-engine stop/waiting
mountall stop/waiting
mounted-debugfs stop/waiting
console stop/waiting
mounted-run stop/waiting
kmod stop/waiting
plymouth-stop stop/waiting
rcS stop/waiting
wait-for-state stop/waiting
flush-early-job-log stop/waiting
friendly-recovery stop/waiting
neutron-metadata-agent stop/waiting
rc-sysinit stop/waiting
neutron-l3-agent stop/waiting
neutron-plugin-openvswitch-agent stop/waiting
umm-br stop/waiting
anacron stop/waiting
udevtrigger stop/waiting
container-detect stop/waiting
mounted-dev stop/waiting
udev-finish stop/waiting
umm-tr stop/waiting
hostname stop/waiting
mountall-reboot stop/waiting
mysql stop/waiting
mountall-shell stop/waiting
mounted-tmp stop/waiting
plymouth-ready stop/waiting
plymouth-splash stop/waiting
plymouth-upstart-bridge stop/waiting
udevmonitor stop/waiting
dmesg stop/waiting
procps stop/waiting
umm-run stop/waiting
console-font stop/waiting
network-interface-container stop/waiting
nova-xenvncproxy stop/waiting
ureadahead stop/waiting

thanks a lot in advance for your help !! best regards, chris

edit flag offensive delete link more

Comments

did you ever solve your issue? I am having the same exact issue with my setup.

kvasko gravatar imagekvasko ( 2016-03-18 21:46:55 -0600 )edit

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

Stats

Asked: 2016-01-11 05:13:37 -0600

Seen: 209 times

Last updated: Jan 12 '16