Bug 1051593
Summary: | "network" script does not correctly bring up ovs bridge devices | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Lars Kellogg-Stedman <lars> |
Component: | openvswitch | Assignee: | Flavio Leitner <fleitner> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 20 | CC: | bderzhavets, chrisw, fleitner, jonathan, kchamart, lars, lnykryn, mrunge, vpavlin, zaitcev |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-07-22 17:55:36 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: |
Description
Lars Kellogg-Stedman
2014-01-10 16:33:28 UTC
I have two phisical nodes Cluster "Controller + Compute + Neutron GRE + Gluster backend for Cinder on ext4 ( due to known bug not "xfs") " been setup per:- http://kashyapc.fedorapeople.org/virt/openstack/neutron-configs-GRE-OVS-two-node.txt && http://kashyapc.fedorapeople.org/virt/openstack/Two-node-Havana-setup.txt Manual Setup - Controller node: Nova, Keystone, Cinder, Glance, Neutron (using Open vSwitch plugin and GRE tunneling ) - Compute node: Nova (nova-compute), Neutron (openvswitch-agent) dwf02.localdomain - Controller (192.168.1.127) dwf01.localdomain - Compute (192.168.1.137) On controller :- $ cat /etc/rc.d/rc.local #!/bin/sh ifdown br-ex ; ifup br-ex ; service network restart ; exit 0 To get properly working OVS bridge be-ex & OVS port p37p1 :- [root@dfw02 ~(keystone_admin)]$ ovs-vsctl show 7d78d536-3612-416e-bce6-24605088212f Bridge br-int Port br-int Interface br-int type: internal Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tapf933e768-42" tag: 1 Interface "tapf933e768-42" Port "tap40dd712c-e4" tag: 1 Interface "tap40dd712c-e4" Bridge br-ex Port "p37p1" Interface "p37p1" Port br-ex Interface br-ex type: internal Port "tap54e34740-87" Interface "tap54e34740-87" Bridge br-tun Port br-tun Interface br-tun type: internal Port "gre-2" Interface "gre-2" type: gre options: {in_key=flow, local_ip="192.168.1.127", out_key=flow, remote_ip="192.168.1.137"} Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: "2.0.0" This looks like to be a dup of bz#1072574. Could you upgrade the openvswitch rpm package accordingly? fbl For the record, I'm including my email to the ovs-discuss mailing list here: It turns out this was due to the following logic in ifup-ovs: if check_device_down "${DEVICE}"; then ovs-vsctl -t ${TIMEOUT} -- --may-exist add-br "$DEVICE" $OVS_OPTIO ${OVS_EXTRA+-- $OVS_EXTRA} \ ${STP+-- set bridge "$DEVICE" stp_enable="${STP}"} else OVSBRIDGECONFIGURED="yes" fi The version of openvswitch currently included in Fedora automatically sets interfaces "up" at boot. This means that the call to check_device_down was always returning false, setting OVSBRIDGECONFIGURED=yes, so the call to ifup-eth later in the script never happens: # When dhcp is not enabled, it is possible that someone may want # a standalone bridge (i.e it may not have any ports). Configure it. if [ "${OVSBOOTPROTO}" != "dhcp" ] && [ -z "${OVSINTF}" ] && \ [ "${OVSBRIDGECONFIGURED}" != "yes" ]; then ${OTHERSCRIPT} ${CONFIG} fi This is fixed upstream in: http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=commitdiff;h=1839c35676b5c3a2a70e83477a6ce3d3c7d0d245 And appears be addressed by the Fedora package generated in response to: https://bugzilla.redhat.com/show_bug.cgi?id=1072574 If I did not missed something, this is bug for ifup-ovs which is in openvswitch package. *** This bug has been marked as a duplicate of bug 1072574 *** |