Your message dated Fri, 29 May 2015 10:08:24 +0200
with message-id <[email protected]>
and subject line Already done
has caused the Debian Bug report #780689,
regarding Missing dependency on conntrack
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 [email protected]
immediately.)
--
780689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780689
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: neutron-l3-agent
Version: 2014.1.3-11
Severity: normal
The L3 agent uses conntrack to purge entries from removed floating IPs.
This was backported to 2014.1.3 but then again removed in 2014.1.4. See
the links below for the details.
As this fixes a (low priority) security issue, I suggest to not revert
this in Debian but to add a dependency on conntrack. And even if this is
not needed for further icehouse updates, the dependency needs to be
added to later releases.
Original bug report: https://bugs.launchpad.net/neutron/+bug/1334926
Fix: https://review.openstack.org/#/c/124375/
Revert: https://review.openstack.org/#/c/132052/
Gaudenz
-- System Information:
Debian Release: 8.0
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'testing'), (100,
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
As much as I can see, python-neutron (on which neutron-l3-agent depends)
already depends on conntrack, and that on both the kilo and icehouse
branch. So this bug isn't relevant anymore.
Cheers,
Thomas
--- End Message ---
