Hello,

We are attempting to hot upgrade OVS and after the upgrade we are running into 
an issue where patch ports do not pass traffic.

We have the following configured:


    Bridge br-int

        fail_mode: secure

        Port "int-br1709"

            Interface "int-br1709"

                type: patch

                options: {peer="phy-br1709"}

        Port "qvo3f046f2c-61"

            tag: 1

            Interface "qvo3f046f2c-61"

        Port "qvode748ec9-02"

            tag: 1

            Interface "qvode748ec9-02"

        Port br-int

            Interface br-int

                type: internal

        Port "qvo929040a5-18"

            tag: 1

            Interface "qvo929040a5-18"

        Port "qvoc9670ef5-c6"

            tag: 1

            Interface "qvoc9670ef5-c6"

        Port "qvoea0bd3f2-7e"

            tag: 1

            Interface "qvoea0bd3f2-7e"

                type: internal

        Port "qvo33d9f79c-fd"

            tag: 1

            Interface "qvo33d9f79c-fd"



    Bridge br-ext

        Port "ext-vlan-1709"

            tag: 1709

            Interface "ext-vlan-1709"

                type: patch

                options: {peer="br1709-ext"}

        Port "bond0"

            Interface "eth2"

            Interface "eth3"

        Port br-ext

            Interface br-ext

                type: internal

    Bridge "br1709"

        Port "br1709"

            Interface "br1709"

                type: internal

        Port "phy-br1709"

            Interface "phy-br1709"

                type: patch

                options: {peer="int-br1709"}

        Port "br1709-ext"

            Interface "br1709-ext"

                type: patch

                options: {peer="ext-vlan-1709"}

Before the upgrade I can tcpdump br1709 and see all traffic that is on vlan 
1709 (ie if I do a tcpdump –n –I eth2 vlan 1709 I see the same traffic).  After 
the upgrade I can still the same traffic eth2, however br1709 only sees traffic 
that’s initiated from within the server.  IE traffic from vms on the 
integration bridge make it out, but the response traffic that I see on both 
br-ext and eth2 never show up on br1706 and thus never make it to the vm's.

I performed the upgrade via:
wget  
http://cbs.centos.org/kojifiles/packages/openvswitch/2.5.0/2.el7/x86_64/openvswitch-2.5.0-2.el7.x86_64.rpm
rpm -Uvh openvswitch-2.5.0-2.el7.x86_64.rpm —noscripts
/usr/share/openvswitch/scripts/ovs-ctl restart

So as I read in the HOT upgrade readme this should preserve all the existing 
flows and configs and basically just swap out the user space pieces.

Everything works with the exact same config/flows after I restart the machine.  
I have tried deleting and reading the patch port from br1709 and br-ext ( 
ext-vlan-1709 and br1709-ext), it does not help.
___________________________________________________________________
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to