← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1205177] Re: VM Ip-address isn't updated when port-info changed on Neutron's side immediately

 

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
       Status: Confirmed => Expired

-- 
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/1205177

Title:
  VM Ip-address isn't updated when port-info changed on Neutron's side
  immediately

Status in OpenStack Compute (nova):
  Expired

Bug description:
  VM Ip-address isn't updated when I change the port-info on Neutron's
  side.

  There are my operations:

  1. Create a VM with a specified port:

  2. Update IP address of this port via Neutron API.

  3. Describe VM from Nova side, the IP is not changed.

  See details here: http://paste.openstack.org/show/41909/

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