Bug 1297975 - Neutron VLAN ranges ignored except for first bridge on 7.2
Neutron VLAN ranges ignored except for first bridge on 7.2
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
urgent Severity high
: y3
: 7.0 (Kilo)
Assigned To: Brad P. Crochet
Itzik Brown
: TestOnly
Depends On:
Blocks: 1243520 1299086
  Show dependency treegraph
Reported: 2016-01-12 16:51 EST by Dan Sneddon
Modified: 2017-10-09 17:16 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1299086 (view as bug list)
Last Closed: 2016-02-18 11:49:03 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dan Sneddon 2016-01-12 16:51:54 EST
Description of problem:
When deploying multiple VLAN bridges, and including the --neutron-vlan-ranges on the command-line, only the first set of VLAN ranges is included in /etc/neutron/plugin.ini

Version-Release number of selected component (if applicable):
OSP-Director 7.2

How reproducible:
100% (I believe)

Steps to Reproduce:
1. Deploy with multiple bridges using --neutron-bridge-mappings datacentre:br-ex,physnet-tenant:br-tenant,floating:br-floating
2. Also use --neutron-vlan-ranges br-tenant:270:420,tenant:160:160

Actual results:
/etc/neutron/plugin.ini has the following:
network_vlan_ranges =br-tenant:270:420

Expected results:
/etc/neutron/plugin.ini should have the following:
network_vlan_ranges =br-tenant:270:420,floating:160:160

Additional info:
This appears to be a regression, in 7.1 the VLAN ranges were put into /etc/neutron/plugin.ini correctly.
Comment 3 Brad P. Crochet 2016-01-20 08:54:44 EST
I was unable to reproduce this on the latest 7.x puddle.
Comment 4 Mike Burns 2016-01-20 12:43:06 EST
Can you please retest with the latest code?
Comment 5 Toni Freger 2016-01-24 06:03:48 EST
Please add "fixed in version" information in order us to start testing this issue.
Comment 6 Itzik Brown 2016-01-25 06:38:46 EST
# openstack overcloud deploy --templates     --control-scale 3 --compute-scale 1 --ntp-server clock.redhat.com  --libvirt-type qemu --neutron-network-vlan-ranges tenant:270:420,floating:160:160 --neutron-bridge-mappings datacentre:br-ex,tenant:br-tenant,floating:br-floating

On the controller I see:

network_vlan_ranges =tenant:270:420,floating:160:160

bridge_mappings =datacentre:br-ex,tenant:br-tenant,floating:br-floating

Comment 8 errata-xmlrpc 2016-02-18 11:49:03 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.