| 2019-05-05 08:54:09 |
Yang Li |
bug |
|
|
added bug |
| 2019-05-05 08:57:38 |
OpenStack Infra |
neutron: status |
New |
In Progress |
|
| 2019-05-05 08:57:38 |
OpenStack Infra |
neutron: assignee |
|
Yang Li (yang-li) |
|
| 2019-05-05 09:05:14 |
Yang Li |
description |
If we have some networks(with dhcp enabled subnets) created, when we want to create a new network
nodes, and the dhcp-agent hasn't been started before in that node. If we start dhcp-agent,
sometimes the network resource won't be synced in this nodes, no network related ns and dnsmasq
process created. The root cause is the function _report_state and sync_state are almost executed
at the same time, if _report_state executed first, everything is fine, but if sync_state executed
first, no network resource will be allocated.
L3-agent will do report_state before resource sync, so there is no problem with router resources. |
If we have some networks(with dhcp enabled subnets) created, when we want to create a new network nodes, and the dhcp-agent hasn't been started before in that node. If we start dhcp-agent, sometimes the network resource won't be synced in this nodes, no network related ns and dnsmasq
process created. The root cause is the function _report_state and sync_state are almost executed at the same time, if _report_state executed first, everything is fine, but if sync_state executed first, no network resource will be allocated.
L3-agent will do report_state before resource sync, so there is no problem with router resources. |
|
| 2019-05-06 12:28:23 |
Lajos Katona |
tags |
|
l3-ipam-dhcp |
|
| 2019-05-08 12:24:12 |
Lajos Katona |
neutron: importance |
Undecided |
Medium |
|
| 2019-05-08 12:53:49 |
Yang Li |
summary |
Network won't be synced when create a new network node |
Network won't be synced when scale a new network node |
|
| 2019-05-08 12:54:08 |
Yang Li |
description |
If we have some networks(with dhcp enabled subnets) created, when we want to create a new network nodes, and the dhcp-agent hasn't been started before in that node. If we start dhcp-agent, sometimes the network resource won't be synced in this nodes, no network related ns and dnsmasq
process created. The root cause is the function _report_state and sync_state are almost executed at the same time, if _report_state executed first, everything is fine, but if sync_state executed first, no network resource will be allocated.
L3-agent will do report_state before resource sync, so there is no problem with router resources. |
If we have some networks(with dhcp enabled subnets) created, when we want to scale a new network nodes, and the dhcp-agent hasn't been started before in that node. If we start dhcp-agent, sometimes the network resource won't be synced in this nodes, no network related ns and dnsmasq
process created. The root cause is the function _report_state and sync_state are almost executed at the same time, if _report_state executed first, everything is fine, but if sync_state executed first, no network resource will be allocated.
L3-agent will do report_state before resource sync, so there is no problem with router resources. |
|
