Bug 1152588
| Summary: | OVS bridge br-ex isn't connected to physical interface according to answer file | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | yfried | ||||
| Component: | openstack-packstack | Assignee: | Javier Peña <jpena> | ||||
| Status: | CLOSED ERRATA | QA Contact: | yfried | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.0 | CC: | aortega, derekh, mmagr, nyechiel, sclewis, tfreger, yeylon | ||||
| Target Milestone: | z5 | Keywords: | AutomationBlocker, Regression, ZStream | ||||
| Target Release: | 4.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | openstack-packstack-2013.2.1-0.33.dev1048.el6ost | Doc Type: | Bug Fix | ||||
| Doc Text: |
Cause: PackStack only associated the OVS external bridge to a physical interface when using vlan tenant networks
Consequence: when creating provider networks using vxlan or GRE tenant networks, the OVS external bridge was not connected to the interface
Fix: updated Neutron plugin in PackStack to connect the OVS external bridge to the physical interface also on the L3 agent, when using vxlan or GRE tenant networks.
Result: external bridge now includes the physical interface.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-10-22 18:41:40 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: | |||||||
| Attachments: |
|
||||||
During preliminary tests, a backport of https://review.openstack.org/#/c/102552/3 fixes the issue. I'm going to run a couple more tests to be on the safe side. If everything goes as expected, I will upload the fix later today. Patch proposed for review -> https://review.openstack.org/128350 Verified On RHEL 6.6
[root@puma48 ~(keystone_yair)]# rpm -qa | grep "neutron\|packstack"
openstack-neutron-2013.2.4-5.el6ost.noarch
python-neutronclient-2.3.4-1.el6ost.noarch
openstack-neutron-ml2-2013.2.4-5.el6ost.noarch
openstack-packstack-2013.2.1-0.33.dev1048.el6ost.noarch
python-neutron-2013.2.4-5.el6ost.noarch
openstack-neutron-openvswitch-2013.2.4-5.el6ost.noarch
openstack-packstack-puppet-2013.2.1-0.33.dev1048.el6ost.noarch
[root@puma48 ~]# ovs-vsctl show
60086aa8-9339-46a4-9244-c43911a7d2cc
Bridge br-int
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port int-br-mybridge
Interface int-br-mybridge
Port br-int
Interface br-int
type: internal
Bridge br-mybridge
Port "eth3"
Interface "eth3"
Port phy-br-mybridge
Interface phy-br-mybridge
Port br-mybridge
Interface br-mybridge
type: internal
Bridge br-tun
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port br-tun
Interface br-tun
type: internal
ovs_version: "1.11.0"
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/RHSA-2014-1691.html |
Created attachment 946892 [details] anser file and packstack logs Description of problem: In "provider" mode, physical interface port isn't added to br-ex even though it's mapped in answer file. As a result - external network is not connected Version-Release number of selected component (if applicable): On RHEL 6.6 [root@puma48 ~(keystone_yair)]# rpm -qa | grep "neutron\|packstack\|puppet" openstack-neutron-2013.2.4-5.el6ost.noarch openstack-packstack-puppet-2013.2.1-0.32.dev1040.el6ost.noarch python-neutronclient-2.3.4-1.el6ost.noarch openstack-neutron-ml2-2013.2.4-5.el6ost.noarch puppet-3.2.4-3.el6_5.noarch openstack-packstack-2013.2.1-0.32.dev1040.el6ost.noarch python-neutron-2013.2.4-5.el6ost.noarch openstack-neutron-openvswitch-2013.2.4-5.el6ost.noarch openstack-puppet-modules-2013.2-9.2.el6ost.noarch How reproducible: Every time Steps to Reproduce: 1. set anwswer file to map br-ex to physical port: [root@puma48 ~(keystone_yair)]# grep "eth\|br-my\|phys" havana_gre_multinode_FILE CONFIG_NEUTRON_ML2_VLAN_RANGES=physnet:181:181 CONFIG_NEUTRON_OVS_VLAN_RANGES=physnet:181:181 CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=physnet:br-mybridge CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-mybridge:eth3 2. run packstack 3. check ovs on networker: ovs-vsctl show Actual results: 9468ce3b-3359-4e3f-920b-ecde72835e0f Bridge br-mybridge Port br-mybridge Interface br-mybridge type: internal Port phy-br-mybridge Interface phy-br-mybridge Expected results: Bridge br-mybridge Port "eth3" Interface "eth3" Port br-mybridge Interface br-mybridge type: internal Port phy-br-mybridge Interface phy-br-mybridge Additional info: workaround - manually add port to bridge: ovs-vsctl add-port br-mybridge eth3