Bug 1299086

Summary: Neutron VLAN ranges ignored except for first bridge on 7.2
Product: Red Hat OpenStack Reporter: Mike Burns <mburns>
Component: rhosp-directorAssignee: Brad P. Crochet <brad>
Status: CLOSED ERRATA QA Contact: Alexander Stafeyev <astafeye>
Severity: high Docs Contact:
Priority: urgent    
Version: 7.0 (Kilo)CC: achernet, brad, dsneddon, gbarros, hbrock, jcoufal, mburns, oblaut, rhel-osp-director-maint, tfreger, yeylon
Target Milestone: gaKeywords: TestOnly
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1297975 Environment:
Last Closed: 2016-04-15 14:31: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:
Bug Depends On: 1297975    
Bug Blocks: 1243520    

Comment 2 Hugh Brock 2016-02-07 14:55:11 UTC
Brad, can you please make sure your fix for  Bug #1297975 is merged on trunk and backported to 8 to fix this?

Comment 3 Brad P. Crochet 2016-02-08 13:31:02 UTC
Please retest on latest 8 poodle/puddle.

Comment 4 Alexander Stafeyev 2016-03-22 10:41:55 UTC
[root@overcloud-novacompute-0 ~]# cat /etc/neutron/plugin.ini | grep vlan_rang
# network_vlan_ranges =
network_vlan_ranges =br-tenant:270:420,tenant:160:160
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2

[stack@undercloud ~]$ rpm -qa| grep heat
openstack-heat-api-cloudwatch-5.0.1-3.el7ost.noarch
python-heatclient-0.8.0-1.el7ost.noarch
openstack-tripleo-heat-templates-kilo-0.8.12-1.el7ost.noarch
openstack-heat-common-5.0.1-3.el7ost.noarch
openstack-heat-api-5.0.1-3.el7ost.noarch
heat-cfntools-1.2.8-2.el7.noarch
openstack-tripleo-heat-templates-0.8.12-1.el7ost.noarch
openstack-heat-engine-5.0.1-3.el7ost.noarch
openstack-heat-api-cfn-5.0.1-3.el7ost.noarch
openstack-heat-templates-0-0.1.20151019.el7ost.noarch

Comment 6 errata-xmlrpc 2016-04-15 14:31: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-0637.html