yahoo-eng-team team mailing list archive

[Shih-Hao Li <shihli@xxxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: Undecided
     Assignee: Shih-Hao Li (shihli)
         Status: In Progress

** Description changed:

- 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.
+ 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.
+ 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.

** Summary changed:

- Fix uuid passing in disable_isolated_metadata_proxy
+ Wrong uuid passed by disable_isolated_metadata_proxy

** Description changed:

  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.
+ 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
+ MatadataDriver can not find the matching process. So the corresponding
  metadata proxy agent can not be destroyed.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1526084

Title:
  Wrong uuid passed by disable_isolated_metadata_proxy

Status in neutron:
  In Progress

Bug 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1526084/+subscriptions