Public bug reported:
Problem
After power down and power off the host, the tenant network is not
available.
The cause is that default flow tables of br-int is not setup
successfully when neutron-openvswitch-agent.starts:
1) The neutron-openvswitch-agent fails to add the flow table 0 but
adds the flow table 23 successfully in setup_default_table(). The flows
look like as follows:
cookie=0x8f4c30f934586d9c, duration=617166.781s, table=0,
n_packets=31822416, n_bytes=2976996304, idle_age=0, hard_age=65534,
priority=2,in_port=1 actions=drop
cookie=0x8f4c30f934586d9c, duration=617167.023s, table=23, n_packets=0,
n_bytes=0, idle_age=65534, hard_age=65534, priority=0 actions=drop
cookie=0x8f4c30f934586d9c, duration=617167.007s, table=24, n_packets=0,
n_bytes=0, idle_age=65534, hard_age=65534, priority=0 actions=drop
2) In the rpc_roop, the neutron-openvswitch-agent will check the ovs
status by checking the flow table 23, and the flow table 23 exists. The
neutron-openvswitch-agent thinks the ovs is normal, but the flow table 0
does not exist and the network connection is not availble.
Affected Neutron version:
Newton
Possible Solution:
Check the default table 0 or check all the default flow tables in
check_ovs_status().
Or add the default flow table 23 first and then add the default table 0 in
setup_default_table()
Thanks
** Affects: neutron
Importance: Undecided
Assignee: sunzuohua (zuohuasun)
Status: New
** Changed in: neutron
Assignee: (unassigned) => sunzuohua (zuohuasun)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1642223
Title:
neutron-openvswitch-agent failed to add default table
Status in neutron:
New
Bug description:
Problem
After power down and power off the host, the tenant network is not
available.
The cause is that default flow tables of br-int is not setup
successfully when neutron-openvswitch-agent.starts:
1) The neutron-openvswitch-agent fails to add the flow table 0 but
adds the flow table 23 successfully in setup_default_table(). The
flows look like as follows:
cookie=0x8f4c30f934586d9c, duration=617166.781s, table=0,
n_packets=31822416, n_bytes=2976996304, idle_age=0, hard_age=65534,
priority=2,in_port=1 actions=drop
cookie=0x8f4c30f934586d9c, duration=617167.023s, table=23, n_packets=0,
n_bytes=0, idle_age=65534, hard_age=65534, priority=0 actions=drop
cookie=0x8f4c30f934586d9c, duration=617167.007s, table=24, n_packets=0,
n_bytes=0, idle_age=65534, hard_age=65534, priority=0 actions=drop
2) In the rpc_roop, the neutron-openvswitch-agent will check the
ovs status by checking the flow table 23, and the flow table 23
exists. The neutron-openvswitch-agent thinks the ovs is normal, but
the flow table 0 does not exist and the network connection is not
availble.
Affected Neutron version:
Newton
Possible Solution:
Check the default table 0 or check all the default flow tables in
check_ovs_status().
Or add the default flow table 23 first and then add the default table 0 in
setup_default_table()
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1642223/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
