Hello community, here is the log from the commit of package openvswitch for openSUSE:Factory checked in at 2016-11-29 12:49:10 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/openvswitch (Old) and /work/SRC/openSUSE:Factory/.openvswitch.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Package is "openvswitch" Changes: -------- --- /work/SRC/openSUSE:Factory/openvswitch/openvswitch-dpdk.changes 2016-11-05 21:27:55.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.openvswitch.new/openvswitch-dpdk.changes 2016-11-29 12:49:10.000000000 +0100 @@ -1,0 +2,13 @@ +Fri Nov 25 16:36:40 UTC 2016 - mchandras@suse.de + +- Relax the DPDK dependency a bit so we can support stable and + possibly new minor releases as well. + +------------------------------------------------------------------- +Mon Nov 21 11:53:00 UTC 2016 - mchandras@suse.de + +- Do not restart the openvswitch service after a package update. + Restarting the systemd service may break connectivity so let the + user decide when it is the best time for such an action. + +------------------------------------------------------------------- openvswitch.changes: same change ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ openvswitch-dpdk.spec ++++++ --- /var/tmp/diff_new_pack.CEoZJv/_old 2016-11-29 12:49:11.000000000 +0100 +++ /var/tmp/diff_new_pack.CEoZJv/_new 2016-11-29 12:49:11.000000000 +0100 @@ -70,8 +70,9 @@ %if %{with dpdk} # We need to be a bit strict with the dpdk version since # it's very possible for DPDK to change it's API between -# releases. This version currently requires 16.07. -BuildRequires: dpdk-devel = 16.07 +# releases. This version currently requires >=16.07 but not +# 17.XX +BuildRequires: dpdk-devel >= 16.07 BuildRequires: libnuma-devel BuildRequires: libpcap-devel # We can't have openvswitch and openvswitch-dpdk in parallel @@ -375,6 +376,14 @@ %postun switch %service_del_postun ovsdb-server.service %service_del_postun ovs-vswitchd.service +# Do not restart the openvswitch service on package updates. +# Restarting the service may break the existing network state. +# For example, openflow rules are not automatically re-installed +# after an OvS update if no SDN controller is used. Moreover, restaring +# the OvS can break remote administration during the update so let the +# admin decide when it's the best time for an OvS restart. +# 5771f476573445710834234a6a9f7bd999a027e7 ("fedora: do not restart the service on a pkg upgrade") +export DISABLE_RESTART_ON_UPDATE=yes %service_del_postun openvswitch.service %pre ovn ++++++ openvswitch.spec ++++++ --- /var/tmp/diff_new_pack.CEoZJv/_old 2016-11-29 12:49:11.000000000 +0100 +++ /var/tmp/diff_new_pack.CEoZJv/_new 2016-11-29 12:49:11.000000000 +0100 @@ -68,8 +68,9 @@ %if %{with dpdk} # We need to be a bit strict with the dpdk version since # it's very possible for DPDK to change it's API between -# releases. This version currently requires 16.07. -BuildRequires: dpdk-devel = 16.07 +# releases. This version currently requires >=16.07 but not +# 17.XX +BuildRequires: dpdk-devel >= 16.07 BuildRequires: libnuma-devel BuildRequires: libpcap-devel # We can't have openvswitch and openvswitch-dpdk in parallel @@ -373,6 +374,14 @@ %postun switch %service_del_postun ovsdb-server.service %service_del_postun ovs-vswitchd.service +# Do not restart the openvswitch service on package updates. +# Restarting the service may break the existing network state. +# For example, openflow rules are not automatically re-installed +# after an OvS update if no SDN controller is used. Moreover, restaring +# the OvS can break remote administration during the update so let the +# admin decide when it's the best time for an OvS restart. +# 5771f476573445710834234a6a9f7bd999a027e7 ("fedora: do not restart the service on a pkg upgrade") +export DISABLE_RESTART_ON_UPDATE=yes %service_del_postun openvswitch.service %pre ovn