| 2016-08-03 03:50:41 |
LIU Yulong |
bug |
|
|
added bug |
| 2016-08-03 03:51:17 |
LIU Yulong |
description |
ENV:
stable/mitaka
hosts:
compute1 (nova-compute, l3-agent (dvr), metedate-agent)
compute2 (nova-compute, l3-agent (dvr), metedate-agent)
network1 (l3-agent (dvr_snat), metedate-agent, dhcp-agent)
network2 (l3-agent(dvr_snat), metedate-agent, dhcp-agent)
How to reproduce? (scenario 1)
set: dhcp_agents_per_network = 2
1. create a DVR router:
neutron router-create --ha False --distributed True test1
2. Create a network & subnet with dhcp enabled.
neutron net-create test1
neutron subnet-create --enable-dhcp test1 --name test1 192.168.190.0/24
3. Attach the router and subnet
neutron router-interface-add test1 subnet=test1
And for another scenario 2：
change the network2 node deployment to only run metedate-agent, dhcp-agent.
Both in the qdhcp-namespace and the VM could ping each other.
So the network node qrouter-namespace is not used.
Code:
The function in following position should not return the DVR router id in scenario 1.
https://github.com/openstack/neutron/blob/master/neutron/db/l3_dvrscheduler_db.py#L249 |
ENV:
stable/mitaka
hosts:
compute1 (nova-compute, l3-agent (dvr), metedate-agent)
compute2 (nova-compute, l3-agent (dvr), metedate-agent)
network1 (l3-agent (dvr_snat), metedata-agent, dhcp-agent)
network2 (l3-agent(dvr_snat), metedata-agent, dhcp-agent)
How to reproduce? (scenario 1)
set: dhcp_agents_per_network = 2
1. create a DVR router:
neutron router-create --ha False --distributed True test1
2. Create a network & subnet with dhcp enabled.
neutron net-create test1
neutron subnet-create --enable-dhcp test1 --name test1 192.168.190.0/24
3. Attach the router and subnet
neutron router-interface-add test1 subnet=test1
And for another scenario 2：
change the network2 node deployment to only run metedata-agent, dhcp-agent.
Both in the qdhcp-namespace and the VM could ping each other.
So the network node qrouter-namespace is not used.
Code:
The function in following position should not return the DVR router id in scenario 1.
https://github.com/openstack/neutron/blob/master/neutron/db/l3_dvrscheduler_db.py#L249 |
|
| 2016-08-03 03:51:50 |
LIU Yulong |
description |
ENV:
stable/mitaka
hosts:
compute1 (nova-compute, l3-agent (dvr), metedate-agent)
compute2 (nova-compute, l3-agent (dvr), metedate-agent)
network1 (l3-agent (dvr_snat), metedata-agent, dhcp-agent)
network2 (l3-agent(dvr_snat), metedata-agent, dhcp-agent)
How to reproduce? (scenario 1)
set: dhcp_agents_per_network = 2
1. create a DVR router:
neutron router-create --ha False --distributed True test1
2. Create a network & subnet with dhcp enabled.
neutron net-create test1
neutron subnet-create --enable-dhcp test1 --name test1 192.168.190.0/24
3. Attach the router and subnet
neutron router-interface-add test1 subnet=test1
And for another scenario 2：
change the network2 node deployment to only run metedata-agent, dhcp-agent.
Both in the qdhcp-namespace and the VM could ping each other.
So the network node qrouter-namespace is not used.
Code:
The function in following position should not return the DVR router id in scenario 1.
https://github.com/openstack/neutron/blob/master/neutron/db/l3_dvrscheduler_db.py#L249 |
ENV:
stable/mitaka
hosts:
compute1 (nova-compute, l3-agent (dvr), metedate-agent)
compute2 (nova-compute, l3-agent (dvr), metedate-agent)
network1 (l3-agent (dvr_snat), metedata-agent, dhcp-agent)
network2 (l3-agent(dvr_snat), metedata-agent, dhcp-agent)
How to reproduce? (scenario 1)
set: dhcp_agents_per_network = 2
1. create a DVR router:
neutron router-create --ha False --distributed True test1
2. Create a network & subnet with dhcp enabled.
neutron net-create test1
neutron subnet-create --enable-dhcp test1 --name test1 192.168.190.0/24
3. Attach the router and subnet
neutron router-interface-add test1 subnet=test1
And for another scenario 2：
change the network2 node deployment to only run metedata-agent, dhcp-agent.
Both in the qdhcp-namespace and the VM could ping each other.
So the network node qrouter-namespace is not used.
Code:
The function in following position should not return the DVR router id in scenario 1.
https://github.com/openstack/neutron/blob/master/neutron/db/l3_dvrscheduler_db.py#L263 |
|
| 2016-08-03 04:04:25 |
LIU Yulong |
description |
ENV:
stable/mitaka
hosts:
compute1 (nova-compute, l3-agent (dvr), metedate-agent)
compute2 (nova-compute, l3-agent (dvr), metedate-agent)
network1 (l3-agent (dvr_snat), metedata-agent, dhcp-agent)
network2 (l3-agent(dvr_snat), metedata-agent, dhcp-agent)
How to reproduce? (scenario 1)
set: dhcp_agents_per_network = 2
1. create a DVR router:
neutron router-create --ha False --distributed True test1
2. Create a network & subnet with dhcp enabled.
neutron net-create test1
neutron subnet-create --enable-dhcp test1 --name test1 192.168.190.0/24
3. Attach the router and subnet
neutron router-interface-add test1 subnet=test1
And for another scenario 2：
change the network2 node deployment to only run metedata-agent, dhcp-agent.
Both in the qdhcp-namespace and the VM could ping each other.
So the network node qrouter-namespace is not used.
Code:
The function in following position should not return the DVR router id in scenario 1.
https://github.com/openstack/neutron/blob/master/neutron/db/l3_dvrscheduler_db.py#L263 |
ENV:
stable/mitaka
hosts:
compute1 (nova-compute, l3-agent (dvr), metedate-agent)
compute2 (nova-compute, l3-agent (dvr), metedate-agent)
network1 (l3-agent (dvr_snat), metedata-agent, dhcp-agent)
network2 (l3-agent(dvr_snat), metedata-agent, dhcp-agent)
How to reproduce? (scenario 1)
set: dhcp_agents_per_network = 2
1. create a DVR router:
neutron router-create --ha False --distributed True test1
2. Create a network & subnet with dhcp enabled.
neutron net-create test1
neutron subnet-create --enable-dhcp test1 --name test1 192.168.190.0/24
3. Attach the router and subnet
neutron router-interface-add test1 subnet=test1
Then the router test1 will exist in both network1 and network2. But in the DB routerl3agentbindings, there is only one record for DVR router to one l3 agent.
And for another scenario 2：
change the network2 node deployment to only run metedata-agent, dhcp-agent.
Both in the qdhcp-namespace and the VM could ping each other.
So the network node qrouter-namespace is not used.
Code:
The function in following position should not return the DVR router id in scenario 1.
https://github.com/openstack/neutron/blob/master/neutron/db/l3_dvrscheduler_db.py#L263 |
|
| 2016-08-03 04:06:20 |
LIU Yulong |
description |
ENV:
stable/mitaka
hosts:
compute1 (nova-compute, l3-agent (dvr), metedate-agent)
compute2 (nova-compute, l3-agent (dvr), metedate-agent)
network1 (l3-agent (dvr_snat), metedata-agent, dhcp-agent)
network2 (l3-agent(dvr_snat), metedata-agent, dhcp-agent)
How to reproduce? (scenario 1)
set: dhcp_agents_per_network = 2
1. create a DVR router:
neutron router-create --ha False --distributed True test1
2. Create a network & subnet with dhcp enabled.
neutron net-create test1
neutron subnet-create --enable-dhcp test1 --name test1 192.168.190.0/24
3. Attach the router and subnet
neutron router-interface-add test1 subnet=test1
Then the router test1 will exist in both network1 and network2. But in the DB routerl3agentbindings, there is only one record for DVR router to one l3 agent.
And for another scenario 2：
change the network2 node deployment to only run metedata-agent, dhcp-agent.
Both in the qdhcp-namespace and the VM could ping each other.
So the network node qrouter-namespace is not used.
Code:
The function in following position should not return the DVR router id in scenario 1.
https://github.com/openstack/neutron/blob/master/neutron/db/l3_dvrscheduler_db.py#L263 |
ENV:
stable/mitaka
hosts:
compute1 (nova-compute, l3-agent (dvr), metedate-agent)
compute2 (nova-compute, l3-agent (dvr), metedate-agent)
network1 (l3-agent (dvr_snat), metedata-agent, dhcp-agent)
network2 (l3-agent(dvr_snat), metedata-agent, dhcp-agent)
How to reproduce? (scenario 1)
set: dhcp_agents_per_network = 2
1. create a DVR router:
neutron router-create --ha False --distributed True test1
2. Create a network & subnet with dhcp enabled.
neutron net-create test1
neutron subnet-create --enable-dhcp test1 --name test1 192.168.190.0/24
3. Attach the router and subnet
neutron router-interface-add test1 subnet=test1
Then the router test1 will exist in both network1 and network2. But in the DB routerl3agentbindings, there is only one record for DVR router to one l3 agent.
And for another scenario 2：
change the network2 node deployment to only run metedata-agent, dhcp-agent.
Both in the qdhcp-namespace and the VM could ping each other.
So qrouter-namespace in the not-binded network node is not used, and should not exist.
Code:
The function in following position should not return the DVR router id in scenario 1.
https://github.com/openstack/neutron/blob/master/neutron/db/l3_dvrscheduler_db.py#L263 |
|
| 2016-08-03 04:22:46 |
LIU Yulong |
neutron: assignee |
|
LIU Yulong (dragon889) |
|
| 2016-08-03 05:25:50 |
LIU Yulong |
neutron: assignee |
LIU Yulong (dragon889) |
|
|
| 2016-08-03 05:26:26 |
LIU Yulong |
description |
ENV:
stable/mitaka
hosts:
compute1 (nova-compute, l3-agent (dvr), metedate-agent)
compute2 (nova-compute, l3-agent (dvr), metedate-agent)
network1 (l3-agent (dvr_snat), metedata-agent, dhcp-agent)
network2 (l3-agent(dvr_snat), metedata-agent, dhcp-agent)
How to reproduce? (scenario 1)
set: dhcp_agents_per_network = 2
1. create a DVR router:
neutron router-create --ha False --distributed True test1
2. Create a network & subnet with dhcp enabled.
neutron net-create test1
neutron subnet-create --enable-dhcp test1 --name test1 192.168.190.0/24
3. Attach the router and subnet
neutron router-interface-add test1 subnet=test1
Then the router test1 will exist in both network1 and network2. But in the DB routerl3agentbindings, there is only one record for DVR router to one l3 agent.
And for another scenario 2：
change the network2 node deployment to only run metedata-agent, dhcp-agent.
Both in the qdhcp-namespace and the VM could ping each other.
So qrouter-namespace in the not-binded network node is not used, and should not exist.
Code:
The function in following position should not return the DVR router id in scenario 1.
https://github.com/openstack/neutron/blob/master/neutron/db/l3_dvrscheduler_db.py#L263 |
ENV:
stable/mitaka
hosts:
compute1 (nova-compute, l3-agent (dvr), metedate-agent)
compute2 (nova-compute, l3-agent (dvr), metedate-agent)
network1 (l3-agent (dvr_snat), metedata-agent, dhcp-agent)
network2 (l3-agent(dvr_snat), metedata-agent, dhcp-agent)
How to reproduce? (scenario 1)
set: dhcp_agents_per_network = 2
1. create a DVR router:
neutron router-create --ha False --distributed True test1
2. Create a network & subnet with dhcp enabled.
neutron net-create test1
neutron subnet-create --enable-dhcp test1 --name test1 192.168.190.0/24
3. Attach the router and subnet
neutron router-interface-add test1 subnet=test1
Then the router test1 will exist in both network1 and network2. But in the DB routerl3agentbindings, there is only one record for DVR router to one l3 agent.
http://paste.openstack.org/show/547695/
And for another scenario 2：
change the network2 node deployment to only run metedata-agent, dhcp-agent.
Both in the qdhcp-namespace and the VM could ping each other.
So qrouter-namespace in the not-binded network node is not used, and should not exist.
Code:
The function in following position should not return the DVR router id in scenario 1.
https://github.com/openstack/neutron/blob/master/neutron/db/l3_dvrscheduler_db.py#L263 |
|
| 2016-08-03 08:39:58 |
LIU Yulong |
tags |
|
l3-dvr-backlog |
|
| 2016-08-03 08:40:26 |
LIU Yulong |
tags |
l3-dvr-backlog |
|
|
| 2016-08-18 09:58:16 |
Armando Migliaccio |
tags |
|
l3-dvr-backlog |
|
| 2016-08-18 09:59:42 |
Armando Migliaccio |
neutron: status |
New |
Incomplete |
|
| 2016-08-19 01:55:31 |
LIU Yulong |
neutron: assignee |
|
LIU Yulong (dragon889) |
|
| 2016-08-19 01:55:33 |
LIU Yulong |
neutron: status |
Incomplete |
In Progress |
|
| 2016-08-31 14:42:01 |
Swaminathan Vasudevan |
neutron: status |
In Progress |
Invalid |
|
| 2016-09-02 09:35:10 |
LIU Yulong |
neutron: status |
Invalid |
In Progress |
|
| 2016-09-02 13:40:56 |
Brian Haley |
bug |
|
|
added subscriber Brian Haley |
| 2016-09-08 08:28:14 |
LIU Yulong |
description |
ENV:
stable/mitaka
hosts:
compute1 (nova-compute, l3-agent (dvr), metedate-agent)
compute2 (nova-compute, l3-agent (dvr), metedate-agent)
network1 (l3-agent (dvr_snat), metedata-agent, dhcp-agent)
network2 (l3-agent(dvr_snat), metedata-agent, dhcp-agent)
How to reproduce? (scenario 1)
set: dhcp_agents_per_network = 2
1. create a DVR router:
neutron router-create --ha False --distributed True test1
2. Create a network & subnet with dhcp enabled.
neutron net-create test1
neutron subnet-create --enable-dhcp test1 --name test1 192.168.190.0/24
3. Attach the router and subnet
neutron router-interface-add test1 subnet=test1
Then the router test1 will exist in both network1 and network2. But in the DB routerl3agentbindings, there is only one record for DVR router to one l3 agent.
http://paste.openstack.org/show/547695/
And for another scenario 2：
change the network2 node deployment to only run metedata-agent, dhcp-agent.
Both in the qdhcp-namespace and the VM could ping each other.
So qrouter-namespace in the not-binded network node is not used, and should not exist.
Code:
The function in following position should not return the DVR router id in scenario 1.
https://github.com/openstack/neutron/blob/master/neutron/db/l3_dvrscheduler_db.py#L263 |
ENV:
stable/mitaka
hosts:
compute1 (nova-compute, l3-agent (dvr), metedate-agent)
compute2 (nova-compute, l3-agent (dvr), metedate-agent)
network1 (l3-agent (dvr_snat), metedata-agent, dhcp-agent)
network2 (l3-agent(dvr_snat), metedata-agent, dhcp-agent)
How to reproduce? (scenario 1)
set: dhcp_agents_per_network = 2
1. create a DVR router:
neutron router-create --ha False --distributed True test1
2. Create a network & subnet with dhcp enabled.
neutron net-create test1
neutron subnet-create --enable-dhcp test1 --name test1 192.168.190.0/24
3. Attach the router and subnet
neutron router-interface-add test1 subnet=test1
Then the router test1 will exist in both network1 and network2. But in the DB routerl3agentbindings, there is only one record for DVR router to one l3 agent.
http://paste.openstack.org/show/547695/
And for another scenario 2：
change the network2 node deployment to only run metedata-agent, dhcp-agent.
Both in the qdhcp-namespace and the VM could ping each other.
So qrouter-namespace in the not-binded network node is not used, and should not exist.
Code:
The essential code issue may be DHCP port should not be considered in DVR host query.
https://github.com/openstack/neutron/blob/master/neutron/common/utils.py#L258 |
|
| 2016-09-08 08:28:49 |
LIU Yulong |
summary |
DVR: dvr router should not exist in not-binded network node |
DVR: dvr router should not exist in not-binded node |
|
| 2016-09-08 09:51:27 |
LIU Yulong |
summary |
DVR: dvr router should not exist in not-binded node |
DVR: dvr router ns should not exist in scheduled DHCP agent nodes |
|
| 2017-10-03 23:13:26 |
Swaminathan Vasudevan |
neutron: importance |
Undecided |
Wishlist |
|
| 2018-07-31 02:15:58 |
LIU Yulong |
neutron: status |
In Progress |
Invalid |
|
| 2018-07-31 02:16:04 |
LIU Yulong |
neutron: assignee |
LIU Yulong (dragon889) |
|
|
| 2019-05-09 15:43:00 |
LIU Yulong |
neutron: status |
Invalid |
Opinion |
|
| 2019-05-09 15:43:11 |
LIU Yulong |
neutron: importance |
Wishlist |
Medium |
|
| 2019-05-24 15:42:37 |
OpenStack Infra |
neutron: status |
Opinion |
In Progress |
|
| 2019-05-24 15:42:37 |
OpenStack Infra |
neutron: assignee |
|
LIU Yulong (dragon889) |
|
| 2019-07-10 18:09:18 |
OpenStack Infra |
neutron: assignee |
LIU Yulong (dragon889) |
Brian Haley (brian-haley) |
|
| 2019-07-11 02:53:34 |
OpenStack Infra |
neutron: assignee |
Brian Haley (brian-haley) |
LIU Yulong (dragon889) |
|
| 2019-07-24 13:13:11 |
LIU Yulong |
neutron: importance |
Medium |
High |
|
| 2019-08-16 18:33:57 |
OpenStack Infra |
neutron: assignee |
LIU Yulong (dragon889) |
Brian Haley (brian-haley) |
|
| 2019-08-21 05:35:28 |
OpenStack Infra |
neutron: assignee |
Brian Haley (brian-haley) |
LIU Yulong (dragon889) |
|
| 2019-08-23 12:27:51 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
| 2019-08-23 15:11:21 |
Bernard Cafarelli |
tags |
l3-dvr-backlog |
l3-dvr-backlog neutron-proactive-backport-potential |
|
| 2019-08-23 21:26:56 |
Swaminathan Vasudevan |
tags |
l3-dvr-backlog neutron-proactive-backport-potential |
l3-dvr-backlog |
|
| 2020-01-29 03:52:43 |
OpenStack Infra |
tags |
l3-dvr-backlog |
in-stable-stein l3-dvr-backlog |
|
| 2020-02-16 11:38:35 |
OpenStack Infra |
tags |
in-stable-stein l3-dvr-backlog |
in-stable-queens in-stable-stein l3-dvr-backlog |
|
| 2020-02-18 17:03:13 |
OpenStack Infra |
tags |
in-stable-queens in-stable-stein l3-dvr-backlog |
in-stable-queens in-stable-rocky in-stable-stein l3-dvr-backlog |
|
