setup_rpc should be the last thing in __init__ method
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
yong sheng gong |
Bug Description
if setup_rpc is too early, the dispatch maybe dispatch the rpc message to an unready agent. take ovs plugin agent for instance,
after setup_rpc is called, many of the initialization work are still needed to be done. If the message is coming during this time, the instance will not be fully initialized:
def __init__(self, integ_br, tun_br, local_ip,
:param integ_br: name of the integration bridge.
:param tun_br: name of the tunnel bridge.
:param local_ip: local IP address of this hypervisor.
:param bridge_mappings: mappings from physical network name to bridge.
:param root_helper: utility to use when running shell cmds.
:param polling_interval: interval (secs) to poll DB.
:param tunnel_types: A list of tunnel types to enable support for in
the agent. If set, will automatically set enable_tunneling to
:param veth_mtu: MTU size for veth interfaces.
:param minimize_polling: Optional, whether to minimize polling by
:param ovsdb_monitor_
the ovsdb monitor.
'''
self.l2_pop = l2_population
'host': cfg.CONF.host,
# Keep track of int_br's device count for use by _report_state()
self.int_br = ovs_lib.
if tunnel_types:
else:
if self.enable_
# Collect additional bridges to monitor
# Security group agent supprot
# Initialize iteration counter
tags: | added: ovs |
description: | updated |
Changed in neutron: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in neutron: | |
milestone: | none → icehouse-2 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | icehouse-2 → 2014.1 |
Fix proposed to branch: master /review. openstack. org/60805
Review: https:/