yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #82389
[Bug 1870569] Re: Unable to create network without default network_segment_range
Reviewed: https://review.opendev.org/717754
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2e6aa290a38798f0eef04231d8424237daf3b2d4
Submitter: Zuul
Branch: master
commit 2e6aa290a38798f0eef04231d8424237daf3b2d4
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date: Mon Apr 6 13:19:57 2020 +0000
Default (shared) network segment range is not mandatory
When "network_segment_range" service extension is enabled, the default
(shared) network segment range could not exist. In this case, when
retrieving the segmentation IDs, the existance of this range should be
checked first.
Change-Id: Iaff891a48adc811ab114fb03b24ab3da9311eec3
Closes-Bug: #1870569
** 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/1870569
Title:
Unable to create network without default network_segment_range
Status in neutron:
Fix Released
Bug description:
When using the network_segment_range, it should be possible to specify
all ranges manually, without any default ranges being required. Until
recently, this was the case, however a recent commit [1] went in that
broke that functionality. Note this bug has also been merged [2] into
stable/train.
This line [3] assumes that there will be a default network segment
range. This should be changed to check if there is a default range,
and if not, then return an empty set, to allow selecting a segment
from the shared and project ranges.
[1] https://opendev.org/openstack/neutron/commit/046672247de56bad950e8267a57bd26205f354a0
[2] https://opendev.org/openstack/neutron/commit/bbe401aaf9bfdd77e1d43d547b2cdb436b1440c8
[3] https://opendev.org/openstack/neutron/src/branch/master/neutron/objects/network_segment_range.py#L197
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1870569/+subscriptions
References