← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1573443] Re: subnet unusable after updating it

 

Reviewed:  https://review.openstack.org/309297
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4d6fe0c38ba5ab822f272af2a892093a315d356a
Submitter: Jenkins
Branch:    master

commit 4d6fe0c38ba5ab822f272af2a892093a315d356a
Author: Kevin Benton <kevin@xxxxxxxxxx>
Date:   Thu Apr 21 19:40:07 2016 -0700

    Use correct session in  update_allocation_pools
    
    This fixes the IP driver update_allocation_pools to use
    the session on the subnet rather than generating a new one.
    Generating a new one was causing the allocation pool
    creation to be uncommitted since nothing was ever starting
    a transaction on the session before it added allocation pool
    objects to the session. This resulted in them never being
    committed to the database so the subnet would become unusable
    after an update.
    
    This also adds a very simple unit test to ensure the
    subnet still works after an update.
    
    Closes-Bug: #1573443
    Change-Id: I1c80a01f475760b9cd405fc89ee2df3a4a1c26c4


** 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/1573443

Title:
  subnet unusable after updating it

Status in neutron:
  Fix Released

Bug description:
  After updating a subnet (e.g. the name or the dhcp_enabled flag), I'm
  no longer able to create ports on the subnet due to an error
  indicating there are no more IP addresses available.

  This was found with ipam_driver = internal

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


References