Ask Your Question
0

kolla "Waiting for virtual IP to appear"

asked 2017-02-13 12:08:23 -0500

Rafael Almeida gravatar image

updated 2017-02-14 07:13:35 -0500

Hi, i'm trying to deploy kolla ansible 4.0.0.0b3 but VIP has not been created. It deploys fluentd, cront, keeplive and haproxy containers then stuck in "TASK [haproxy : Waiting for virtual IP to appear]" until timedout operation.

I did not found any error or exception in any created containers log.

Error message

TASK [haproxy : Starting haproxy container] ************************************
changed: [controller] => {"changed": true, "result": false}

TASK [haproxy : Starting keepalived container] *********************************
changed: [controller] => {"changed": true, "result": false}

TASK [haproxy : Ensuring latest haproxy config is used] ************************
ok: [controller] => {"changed": false, "cmd": ["docker", "exec", "haproxy", "/usr/local/bin/kolla_ensure_haproxy_latest_config"], "delta": "0:00:00.057160", "end": "2017-02-14 10:24:23.102365", "rc": 0, "start": "2017-02-14 10:24:23.045205", "stderr": "", "stdout": "", "stdout_lines": [], "warnings": []}

TASK [haproxy : Waiting for virtual IP to appear] ******************************
fatal: [controller]: FAILED! => {"changed": false, "elapsed": 301, "failed": true, "msg": "Timeout when waiting for 10.10.0.250:3306"}
    to retry, use: --limit @/usr/share/kolla/ansible/site.retry

docker ps on my controller node:

CONTAINER ID        IMAGE                                      COMMAND             CREATED             STATUS              PORTS               NAMES
730e7c79d1f5        kolla/centos-binary-keepalived:master      "kolla_start"       23 seconds ago      Up 23 seconds                           keepalived
ef45371e0d15        kolla/centos-binary-haproxy:master         "kolla_start"       23 seconds ago      Up 23 seconds                           haproxy
2b33d4fa4ed5        kolla/centos-binary-cron:master            "kolla_start"       29 seconds ago      Up 29 seconds                           cron
4703b01ba847        kolla/centos-binary-kolla-toolbox:master   "kolla_start"       31 seconds ago      Up 31 seconds                           kolla_toolbox
e0e03f24e7fb        kolla/centos-binary-fluentd:master         "kolla_start"       32 seconds ago      Up 31 seconds

/etc/kolla/globals.yml

config_strategy: "COPY_ALWAYS"
kolla_base_distro: "centos"
kolla_install_type: "binary"
openstack_release: "master"
node_custom_config: "/etc/kolla/config"
kolla_internal_vip_address: "10.10.0.250"
network_interface: "eth0"
neutron_external_interface: "eth1"
designate_backend: "bind9"
designate_ns_record: "sample.openstack.org"
tempest_image_id:
tempest_flavor_ref_id:
tempest_public_network_id:
tempest_floating_network_name:

Keepalived logs

bogus VRRP packet received on eth0 !!!
Keepalived_vrrp[14]: bogus VRRP packet received on eth0 !!!
VRRP_Instance(kolla_internal_vip_51) ignoring received advertisment...
Keepalived_vrrp[14]: VRRP_Instance(kolla_internal_vip_51) ignoring received advertisment...
ip address associated with VRID not present in received packet : 10.10.0.250
Keepalived_vrrp[14]: ip address associated with VRID not present in received packet : 10.10.0.250
one or more VIP associated with VRID mismatch actual MASTER advert
Keepalived_vrrp[14]: one or more VIP associated with VRID mismatch actual MASTER advert
bogus VRRP packet received on eth0 !!!
Keepalived_vrrp[14]: bogus VRRP packet received on eth0 !!!
VRRP_Instance(kolla_internal_vip_51) ignoring received advertisment...
Keepalived_vrrp[14]: VRRP_Instance(kolla_internal_vip_51) ignoring received advertisment...
ip address associated with VRID not present in received packet : 10.10.0.250
Keepalived_vrrp[14]: ip address associated with VRID not present in received packet : 10.10.0.250
one or more VIP associated with VRID mismatch actual MASTER advert
Keepalived_vrrp[14]: one or more VIP associated with VRID mismatch actual MASTER advert
bogus VRRP packet received on eth0 !!!
Keepalived_vrrp[14]: bogus VRRP packet received on eth0 !!!
VRRP_Instance(kolla_internal_vip_51) ignoring received advertisment...
Keepalived_vrrp[14]: VRRP_Instance(kolla_internal_vip_51) ignoring received advertisment...
ip address associated with VRID not present in received packet : 10.10.0.250
Keepalived_vrrp[14]: ip address associated with VRID not present in received packet : 10.10.0.250
one or more VIP associated with VRID mismatch actual MASTER advert
Keepalived_vrrp[14]: one or more VIP ...
(more)
edit retag flag offensive close merge delete

Comments

Can you share globals.yml, "ip a" output, docker ps -a and docker logs keepalived, docker logs haproxy. And logs(if present) at /var/lib/docker/volumes/kolla_log/_data/haproxy?

Eduardo Gonzalez gravatar imageEduardo Gonzalez ( 2017-02-14 05:50:42 -0500 )edit

Hi Eduardo, https://gist.github.com/rafaelsisweb/c55f1b6f28c4fedc21cd3aee0125f673 (link text)

Rafael Almeida gravatar imageRafael Almeida ( 2017-02-14 06:32:19 -0500 )edit

Is there any other VRRP service using ID 51 in the network? Firewall blocking connections, selinux? Do kolla-ansible prechecks passed?

Eduardo Gonzalez gravatar imageEduardo Gonzalez ( 2017-02-14 07:03:45 -0500 )edit

Are passwords in /etc/kolla/passwords.yml generated? Seems like an auth issue

Eduardo Gonzalez gravatar imageEduardo Gonzalez ( 2017-02-14 07:06:42 -0500 )edit

I'm going to edit the question and add the content in the link provided, so other users have an easier way to find similar issues as ask.openstack.org is indexed by search engines. Now I'm almost sure that passwords are not generated (happened me some times)

Eduardo Gonzalez gravatar imageEduardo Gonzalez ( 2017-02-14 07:08:31 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
1

answered 2017-02-14 09:35:32 -0500

Hi, I'm going to summarize the issue here and common issues, so other users may find useful this info.

When hangs on Waiting for virtual IP to appear task this are the common issues and solution:

Other service in the network is using the same VRRP VRID, by default 51

  • Change default keepalived_virtual_router_id to other value (Must be free in the network)

Password file is not filled.

  • Execute kolla-genpwd command to fill the file present at /etc/kolla/passwords.yml

Network is not properly configured. Eg: kolla_internal_vip_address is not accessible from network_interface.

  • Ensure kolla-ansible prechecks pass
  • Make sure IP address is accessible from network_interface

Firewall blocking connection or some SElinux policy is denying the action.

  • Check and open firewall rules
  • See what SElinux is denying with audit2allow -aw and take action.

Regards

edit flag offensive delete link more

Comments

Hi, I am having some confusions.

Does kolla_internal_vip_address need to be in the same network as network_interface ? Let's say neutron_external_interface is connected to my external network and kolla_internal_vip is having an IP from the external network too. Will it work?

nahian gravatar imagenahian ( 2018-02-26 04:08:19 -0500 )edit

Yes if you are using different interfaces and share same network as network_interface.

internal_vip should be in same network as api_interface (network_interface by default). This requirement is checked in prechecks task

Eduardo Gonzalez gravatar imageEduardo Gonzalez ( 2018-02-26 08:02:33 -0500 )edit

Thanks Eduardo, I have succeeded in deploying Kolla-ansible Pike on top of OpenStack. I would call it Virtual kolla. It was for testing purpose though.

nahian gravatar imagenahian ( 2018-03-15 10:51:35 -0500 )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

1 follower

Stats

Asked: 2017-02-13 12:08:23 -0500

Seen: 1,819 times

Last updated: Feb 14 '17