[Openstack-security] [Bug 1840895] Fix merged to neutron (stable/queens)

OpenStack Infra 1840895 at bugs.launchpad.net
Thu Sep 19 16:37:54 UTC 2019


Reviewed:  https://review.opendev.org/682559
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=17f3b75007643e8329eb93194d2e9597be3b90fb
Submitter: Zuul
Branch:    stable/queens

commit 17f3b75007643e8329eb93194d2e9597be3b90fb
Author: Slawek Kaplonski <skaplons at redhat.com>
Date:   Fri Aug 30 22:32:19 2019 +0200

    Fix creation of vlan network with segmentation_id set to 0
    
    In case when vlan network was created with segmentation_id=0 and without
    physical_network given, it was passing validation of provider segment
    and first available segmentation_id was choosen for network.
    Problem was that in such case all available segmentation ids where
    allocated and no other vlan network could be created later.
    
    This patch fixes validation of segmentation_id when it is set to value 0.
    
    Change-Id: Ic768deb84d544db832367f9a4b84a92729eee620
    Closes-bug: #1840895
    (cherry picked from commit f01f3ae5dd0dd7dd9aa513a1b50e04e20a08b97b)

-- 
You received this bug notification because you are a member of OpenStack
Security SIG, which is subscribed to OpenStack.
https://bugs.launchpad.net/bugs/1840895

Title:
  segment parameter check failed when creating network

Status in neutron:
  Fix Released
Status in OpenStack Security Advisory:
  Won't Fix

Bug description:
  neutron net-create test --provider:network_type vlan
  --provider:segmentation_id 0

  Execute commands like this, all vlan in ml2_vlan_allocations table is
  set to allocated, no vlan network can be created.

  validate_provider_segment function should check whether
  provider:segmentation_id is 0.

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



More information about the Openstack-security mailing list