Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1297975

Summary:	Neutron VLAN ranges ignored except for first bridge on 7.2
Product:	Red Hat OpenStack	Reporter:	Dan Sneddon <dsneddon>
Component:	rhosp-director	Assignee:	Brad P. Crochet <brad>
Status:	CLOSED ERRATA	QA Contact:	Itzik Brown <itbrown>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	7.0 (Kilo)	CC:	akrivoka, brad, dmacpher, dsneddon, gbarros, jcoufal, mburns, oblaut, rhel-osp-director-maint
Target Milestone:	y3	Keywords:	TestOnly
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1299086 (view as bug list)		Environment:
Last Closed:	2016-02-18 16:49:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1243520, 1299086

Description Dan Sneddon 2016-01-12 21:51:54 UTC

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
3.

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 13:54:44 UTC

I was unable to reproduce this on the latest 7.x puddle.

Comment 4 Mike Burns 2016-01-20 17:43:06 UTC

Can you please retest with the latest code?

Comment 5 Toni Freger 2016-01-24 11:03:48 UTC

Please add "fixed in version" information in order us to start testing this issue.

Comment 6 Itzik Brown 2016-01-25 11:38:46 UTC

Ran:
# 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:

/etc/neutron/plugin.ini
========================
network_vlan_ranges =tenant:270:420,floating:160:160

/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini
=======================================================
bridge_mappings =datacentre:br-ex,tenant:br-tenant,floating:br-floating

Version
=============
openstack-tripleo-puppet-elements-0.0.1-5.el7ost.noarch
openstack-tripleo-common-0.0.1.dev6-5.git49b57eb.el7ost.noarch
openstack-tripleo-heat-templates-0.8.6-111.el7ost.noarch
openstack-tripleo-image-elements-0.9.6-10.el7ost.noarch
openstack-tripleo-0.0.7-0.1.1664e566.el7ost.noarch
openstack-puppet-modules-2015.1.8-43.el7ost.noarch
openstack-tripleo-puppet-elements-0.0.1-5.el7ost.noarch
python-neutron-2015.1.2-7.el7ost.noarch
openstack-neutron-2015.1.2-7.el7ost.noarch

Comment 8 errata-xmlrpc 2016-02-18 16:49:03 UTC

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.

https://rhn.redhat.com/errata/RHBA-2016-0264.html