Bug#777601: systemd: Loosing LXC memory cgroups after service install

[Luca Bruno]

Control: unarchive -1

On Thu, 12 Feb 2015 15:43:30 +0100 Martin Pitt <mpitt at debian.org> wrote:
> Hello again,
>
> so the patch that got proposed at
>
>
http://lists.freedesktop.org/archives/systemd-devel/2014-September/023276.html
>
> actually makes a lot of sense: This makes systemd only clean up
> cgroups that it created by itself, and thus won't clean up empty ones
> in other controllers that LXC created. I tested this and committed
> this for the experimental branch for now:
>
>
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=experimental&id=286ef78fd
>
> I'd like to see this out in the wild for some time before applying it
> to jessie, though. I'm also still interested in what the actual impact
> of that is -- critical seems rather inflated? Losing empty cgroups
> doesn't sound that dangerous after all, aside from the LXC warnings
> when shutting down a container?
>
> Thanks,

I've tried this patch and looks like adding another bug to me. Please
confirm what I'm experiencing. It's true, it does not remove cgroups
created by systemd, but then it doesn't cleanup cgroups that systemd
created either.

Example:

1) set MemoryLimit to a service, the memory limit will appear in the cgroups
2) unset MemoryLimit to the same service, reload daemon, restart,
disable, re-enable, whatever... but the memory limit will NOT disappear
from the cgroups

Seems wrong and possibly worse to me.

Best regards,