yahoo-eng-team team mailing list archive

[OpenStack Infra <1521524@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/251718
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=87ce73141dddb840ffc523f253fdf87aef11d1c7
Submitter: Jenkins
Branch:    master

commit 87ce73141dddb840ffc523f253fdf87aef11d1c7
Author: Oleg Bondarev <obondarev@xxxxxxxxxxxx>
Date:   Tue Dec 1 11:47:05 2015 +0300

    Notify about port create/update unconditionally
    
    The notification about port create/update should be done no matter
    if host (or any other field) was changed or not - it should be up to
    handler to decide how to handle it.
    
    This also fixes the bug when there was actually no notification to l3
    dvr agent on compute node on new port creation:
    _get_host_port_if_changed() always returned None - this is a regression
    from commit 2ee08c3464c53abaf9bc5493132ad7958611e3b8
    
    Closes-Bug: #1521524
    Change-Id: I5bb416d2aaab632526f06a5620c0a4ea96340d21


** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
  With DVR enabled instances sometimes fail to get metadata

Status in neutron:
  Fix Released

Bug description:
  Rally scenario which creates VMs with floating IPs at a high rate
  sometimes fails with SSHTimeout when trying to connect to the VM by
  floating IP. At the same time pings to the VM are fine.

  It appeared that VMs may sometimes fail to get public key from
  metadata. That happens because metadata proxy process was started
  after VM boot.

  Further analysis showed that l3 agent on compute node was not notified
  about new VM port at the time this port was created.

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