| 2015-12-14 22:30:52 |
Shih-Hao Li |
bug |
|
|
added bug |
| 2015-12-14 22:32:16 |
Shih-Hao Li |
description |
In DhcpAgent, when enable_isolated_metadata_proxy() spawns a metadata proxy agent
for a network, it will pass router_id instead of network_id if metadata network is enabled
and a router port is connected to this network. Later, MatadataDriver will register this uuid
(i.e. router_id) with monitor for the new metadata proxy process.
But when disable_isolated_metadata_proxy() destroys a metadata proxy agent for a network,
it always passes network_id as the uuid. Thus MatadataDriver can not find the matching process.
So the corresponding metadata proxy agent can not be destroyed. |
In DhcpAgent, when enable_isolated_metadata_proxy() spawns a metadata proxy agent for a network, it will pass router_id instead of network_id if metadata network is enabled and a router port is connected to this network. Later, MatadataDriver will register this uuid (i.e. router_id) with monitor for the new metadata proxy process.
But when disable_isolated_metadata_proxy() destroys a metadata proxy agent for a network, it always passes network_id as the uuid. Thus MatadataDriver can not find the matching process.So the corresponding metadata proxy agent can not be destroyed. |
|
| 2015-12-14 22:34:37 |
Shih-Hao Li |
summary |
Fix uuid passing in disable_isolated_metadata_proxy |
Wrong uuid passed by disable_isolated_metadata_proxy |
|
| 2015-12-14 22:36:55 |
Shih-Hao Li |
description |
In DhcpAgent, when enable_isolated_metadata_proxy() spawns a metadata proxy agent for a network, it will pass router_id instead of network_id if metadata network is enabled and a router port is connected to this network. Later, MatadataDriver will register this uuid (i.e. router_id) with monitor for the new metadata proxy process.
But when disable_isolated_metadata_proxy() destroys a metadata proxy agent for a network, it always passes network_id as the uuid. Thus MatadataDriver can not find the matching process.So the corresponding metadata proxy agent can not be destroyed. |
In DhcpAgent, when enable_isolated_metadata_proxy() spawns a metadata proxy agent for a network, it will pass router_id instead of network_id if metadata network is enabled and a router port is connected to this network.
Later, MatadataDriver will register this uuid (i.e. router_id) with monitor for the new metadata proxy process.
But when disable_isolated_metadata_proxy() destroys a metadata proxy agent for a network, it always passes network_id as the uuid. Thus MatadataDriver can not find the matching process. So the corresponding metadata proxy agent can not be destroyed. |
|
| 2015-12-14 22:38:17 |
OpenStack Infra |
neutron: status |
New |
In Progress |
|
| 2015-12-14 22:38:17 |
OpenStack Infra |
neutron: assignee |
|
Shih-Hao Li (shihli) |
|
| 2015-12-15 00:04:42 |
Henry Gessau |
tags |
|
l3-ipam-dhcp |
|
| 2015-12-15 00:04:54 |
Henry Gessau |
neutron: importance |
Undecided |
Medium |
|
| 2015-12-15 03:54:10 |
Shih-Hao Li |
description |
In DhcpAgent, when enable_isolated_metadata_proxy() spawns a metadata proxy agent for a network, it will pass router_id instead of network_id if metadata network is enabled and a router port is connected to this network.
Later, MatadataDriver will register this uuid (i.e. router_id) with monitor for the new metadata proxy process.
But when disable_isolated_metadata_proxy() destroys a metadata proxy agent for a network, it always passes network_id as the uuid. Thus MatadataDriver can not find the matching process. So the corresponding metadata proxy agent can not be destroyed. |
In DhcpAgent, when enable_isolated_metadata_proxy() spawns a metadata proxy agent for a network, it will pass router_id instead of network_id if metadata network is enabled and a router port is connected to this network.
Later, MetadataDriver will register this uuid (i.e. router_id) with monitor for the new metadata proxy process.
But when disable_isolated_metadata_proxy() destroys a metadata proxy agent for a network, it always passes network_id as the uuid. Thus MetadataDriver can not find the matching process. So the corresponding metadata proxy agent can not be destroyed. |
|
| 2016-01-05 04:44:28 |
OpenStack Infra |
neutron: assignee |
Shih-Hao Li (shihli) |
Armando Migliaccio (armando-migliaccio) |
|
| 2016-01-08 00:25:34 |
OpenStack Infra |
neutron: assignee |
Armando Migliaccio (armando-migliaccio) |
Shih-Hao Li (shihli) |
|
| 2016-01-09 04:24:38 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
