yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #57102
[Bug 1511722] Re: VM loses connectivity on floating ip association when using l3_ha
Reviewed: https://review.openstack.org/343312
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b3af52e7388423a5fd3872453512218b00a5c6d7
Submitter: Jenkins
Branch: master
commit b3af52e7388423a5fd3872453512218b00a5c6d7
Author: Stefan Nica <nica.stefan.daniel@xxxxxxxxx>
Date: Sun Jul 17 16:36:08 2016 +0300
Keepalived global_defs configuration entries required to avoid DNS lookup
This changeset addresses a particular L3-HA Neutron deployment scenario
in which the DNS server configured for the management network is not
also accessible from the virtual router namespace (i.e. over the
external network).
Keepalived uses the hostname against getaddrinfo twice to set default
values for the router_id and notification_email_from global configuration
attributes. If the hostname cannot be resolved through /etc/hosts and
if the nameserver is not reachable, long delays are incurred during
keepalived startup and configuration reload, causing VRRP state flapping
and dropped traffic over floating IPs.
Setting router_id and notification_email_from in the keepalived
configuration avoids unnecessary DNS lookups. However, this solution
is only effective with keepalived >= 1.2.17. Older versions still
exhibit the same problem with or without this patch.
Closes-Bug: #1511722
Change-Id: If6e31d164bd6ade52997bc0073ef50cdbc99ec93
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1511722
Title:
VM loses connectivity on floating ip association when using l3_ha
Status in neutron:
Fix Released
Bug description:
I not sure if my issue is related to this bug
https://bugs.launchpad.net/neutron/+bug/1389880, it's new one or it's
a misconfiguration, but I have the same symptoms.
If I create a new router in HA ( # neutron router-create --ha=True
router01), everything works fine.
When I create a new router without HA flag, if I have an instance with
one floating IP and then I assign a floating IP to other instance, I
lose external connectivity to both instance (doesn't matter the number
of instances, I lose external connectivity with all of them) until I
connect to anyone by vnc and I ping to external/internet IP, and then
everything works fine again.
Sorry, English is not my native language.
Ubuntu 14.04
Open vSwitch 2.3.2
Kilo 2015.1.1
root@network01:/home/administrator# cat /etc/neutron/neutron.conf | grep -v ^$ | grep -v ^#
[DEFAULT]
verbose = False
rpc_backend = rabbit
auth_strategy = keystone
core_plugin = ml2
service_plugins = router
allow_overlapping_ips = True
dhcp_agents_per_network = 2
l3_ha = True
max_l3_agents_per_router = 2
min_l2_agents_per_router = 2
[matchmaker_redis]
[matchmaker_ring]
[quotas]
[agent]
root_helper = sudo /usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf
[keystone_authtoken]
auth_uri = http://10.8.11.120:5000
auth_url = http://10.8.11.120:35357
auth_plugin = password
project_domain_id = default
user_domain_id = default
project_name = service
username = neutron
password = secret
[database]
[nova]
[oslo_concurrency]
lock_path = $state_path/lock
[oslo_policy]
[oslo_messaging_amqp]
[oslo_messaging_qpid]
[oslo_messaging_rabbit]
rabbit_hosts = controller01:5672,controller02:5672
rabbit_userid = openstack
rabbit_password = secret
rabbit_retry_interval = 1
rabbit_retry_backoff = 2
rabbit_max_retries = 0
rabbit_durable_queues = True
rabbit_ha_queues = True
root@network01:/home/administrator# cat /etc/neutron/l3_agent.ini | grep -v ^$ | grep -v ^#
[DEFAULT]
verbose = True
interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
external_network_bridge =
router_delete_namespaces = True
root@network01:/home/administrator# cat /etc/neutron/plugins/ml2/ml2_conf.ini | grep -v ^$ | grep -v ^#
[ml2]
type_drivers = flat,vlan,gre,vxlan
tenant_network_types = gre
mechanism_drivers = openvswitch
[ml2_type_flat]
flat_networks = external
[ml2_type_vlan]
[ml2_type_gre]
tunnel_id_ranges = 1:1000
[ml2_type_vxlan]
[securitygroup]
enable_security_group = True
enable_ipset = True
firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
[ovs]
local_ip = 192.168.0.101
bridge_mappings = external:br-ex
[agent]
tunnel_types = gre
root@compute01:/home/ubuntu# cat /etc/neutron/neutron.conf | grep -v ^$ | grep -v ^#
[DEFAULT]
verbose = True
rpc_backend = rabbit
auth_strategy = keystone
core_plugin = ml2
service_plugins = router
allow_overlapping_ips = True
[matchmaker_redis]
[matchmaker_ring]
[quotas]
[agent]
root_helper = sudo /usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf
[keystone_authtoken]
auth_uri = http://10.8.11.120:5000
auth_url = http://10.8.11.120:35357
auth_plugin = password
project_domain_id = default
user_domain_id = default
project_name = service
username = neutron
password = secret
[database]
[nova]
[oslo_concurrency]
lock_path = $state_path/lock
[oslo_policy]
[oslo_messaging_amqp]
[oslo_messaging_qpid]
[oslo_messaging_rabbit]
rabbit_hosts = controller01:5672,controller02:5672
rabbit_userid = openstack
rabbit_password = secret
rabbit_retry_interval = 1
rabbit_retry_backoff = 2
rabbit_max_retries = 0
rabbit_durable_queues = True
rabbit_ha_queues = True
root@compute01:/home/ubuntu# cat /etc/neutron/plugins/ml2/ml2_conf.ini | grep -v ^$ | grep -v ^#
[ml2]
type_drivers = flat,vlan,gre,vxlan
tenant_network_types = gre
mechanism_drivers = openvswitch
[ml2_type_flat]
[ml2_type_vlan]
[ml2_type_gre]
tunnel_id_ranges = 1:1000
[ml2_type_vxlan]
[securitygroup]
enable_security_group = True
enable_ipset = True
firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
[ovs]
local_ip = 192.168.0.105
[agent]
tunnel_types = gre
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1511722/+subscriptions
References