Your message dated Mon, 15 Apr 2019 07:22:00 +0000
with message-id <f817b178-a6bc-217d-d6b0-ed921ed10...@thykier.net>
and subject line Re: Bug#927107: unblock:
openvswitch/2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12
has caused the Debian Bug report #927107,
regarding unblock: openvswitch/2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
927107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: unblock
Please unblock package openvswitch
As per the one liner attached debdiff, this Debian release -12 fixes
the debian/ifupdown.sh script which ends up in:
/etc/network/if-{pre-up,post-down}.d/openvswitch
When using an OVSBond interface, the script wasn't using --may-exist,
and as a consequence, may fail setting-up network interfaces in case
the bond already exists.
Note that the same change was commited upstream recently.
unblock openvswitch/2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12
diff -Nru openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/changelog
openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/changelog
--- openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/changelog
2019-03-31 00:50:26.000000000 +0100
+++ openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/changelog
2019-04-14 00:25:19.000000000 +0200
@@ -1,3 +1,10 @@
+openvswitch (2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12) unstable; urgency=medium
+
+ * Add --may-exist in debian/ifupdown.sh as per upstream commit. Without it,
+ networking service may fail (Closes: #926942).
+
+ -- Thomas Goirand <z...@debian.org> Sun, 14 Apr 2019 00:25:19 +0200
+
openvswitch (2.10.0+2018.08.28+git.8ca7c82b7d+ds1-11) unstable; urgency=medium
* Removes network.service from openvswitch-switch.service to avoid a
diff -Nru openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/ifupdown.sh
openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/ifupdown.sh
--- openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/ifupdown.sh
2019-03-31 00:50:26.000000000 +0100
+++ openvswitch-2.10.0+2018.08.28+git.8ca7c82b7d+ds1/debian/ifupdown.sh
2019-04-14 00:25:19.000000000 +0200
@@ -67,7 +67,7 @@
ip link set "${IFACE}" up
;;
OVSBond)
- ovs_vsctl -- --fake-iface add-bond "${IF_OVS_BRIDGE}"\
+ ovs_vsctl -- --fake-iface --may-exist add-bond
"${IF_OVS_BRIDGE}"\
"${IFACE}" ${IF_OVS_BONDS} ${IF_OVS_OPTIONS} \
${OVS_EXTRA+-- $OVS_EXTRA}
--- End Message ---
--- Begin Message ---
Thomas Goirand:
> Package: release.debian.org
> Severity: normal
> User: release.debian....@packages.debian.org
> Usertags: unblock
>
> Please unblock package openvswitch
>
> As per the one liner attached debdiff, this Debian release -12 fixes
> the debian/ifupdown.sh script which ends up in:
> /etc/network/if-{pre-up,post-down}.d/openvswitch
>
> When using an OVSBond interface, the script wasn't using --may-exist,
> and as a consequence, may fail setting-up network interfaces in case
> the bond already exists.
>
> Note that the same change was commited upstream recently.
>
> unblock openvswitch/2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12
>
Unblocked, thanks.
~Niels
--- End Message ---
