l3 agent HA communication failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
New
|
Undecided
|
Unassigned |
Bug Description
An openstack environment was built using Openstack-Ansible (OSA) on Mitaka with the neutron_l3_agent in HA mode. This was functioning correctly using network namespaces for routers. Within the namespace keeplived created an 'ha' virtual interface to track the status of the other instance of the virtual router. This worked correctly, the 'ha' virtual interface within 'master' router namespace could ping the 'ha' virtual interface within the 'backup' router namespace, and when the master went offline keepalived would successfully transition to master and bring up the virtual IP addresses with then network namespace virtual router.
We upgraded the environment to newton via the guide at http://
******** l3_agent.ini configuration ********
# General
[DEFAULT]
verbose = True
debug = False
# While this option is deprecated in Liberty, if we remove it then it takes
# a default value of 'br-ex', which we do not want. We therefore leave it
# in place for now and can remove it in Mitaka.
external_
gateway_
use_namespaces = True
router_
# Drivers
interface_driver = neutron.
# Agent mode (legacy only)
agent_mode = legacy
# Conventional failover
allow_automatic
# HA failover
ha_confs_path = /var/lib/
ha_vrrp_advert_int = 2
ha_vrrp_
ha_vrrp_auth_type = PASS
handle_
send_arp_for_ha = 3
# Metadata
enable_
******** keepalived.conf configuration ********
vrrp_instance VR_1 {
state BACKUP
interface ha-42c56d27-10
virtual_
priority 50
garp_
nopreempt
advert_int 2
authentication {
auth_type PASS
auth_pass bee916a2589b14dd7f
}
track_interface {
}
virtual_
}
virtual_
10.0.0.1/8 dev qr-8deaf807-bb
}
virtual_routes {
0.0.0.0/0 via xx.xx.xx.xx dev qg-6e4ebe51-94
}
}
tags: | added: l3-ha |
Do you know if l2population is in use here after the upgrade? Are only the HA networks affected, or are you also unable to ping from the router or DHCP namespaces to the instances?