yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1194178] Re: Host is always set to None in get_instance_nw_info(...)

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Wed, 17 Jul 2013 12:17:47 -0000
Reply-to: Bug 1194178 <1194178@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => havana-2

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1194178

Title:
  Host is always set to None in get_instance_nw_info(...)

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) folsom series:
  New
Status in OpenStack Compute (nova) grizzly series:
  In Progress

Bug description:
  The the nova-network manager's method get_instance_nw_info(...) the
  host parameter get reset to None.

  This causes the host to be interpreted as the host where the nova-
  network process is running instead of the host that is passed in
  (which is usually the host where the instance lives). One side affect
  of this change is that the address of the DHCP server for an instance
  can get assigned to a random host depending on which nova-network
  process handles the get_instance_nw_info(...) call instead of the host
  where the instance exists.

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