[systemd-devel] stop+start of nspawn scope aborts: 's->state == SCOPE_DEAD'

[Lennart Poettering]

On Mon, 12.08.13 19:41, Marti Raudsepp (marti at juffo.org) wrote:

> Hi list,
> 
> I hit a bug today in the "scope" unit support. Reproducible like this:
> 
> systemd-nspawn -bD /srv/subarch
> systemctl stop machine-subarch.scope
> systemctl start machine-subarch.scope
> 
> I wasn't sure whether "start" would do anything or not so I gave it a
> shot, but it turned out to crash the host systemd with:
> 
> Assertion 's->state == SCOPE_DEAD' failed at src/core/scope.c:246,
> function scope_start(). Aborting....
> 
> Tested with systemd 206 as well as current git master
> (206.103.g631c922) on Arch Linux.
> 
> /srv/subarch is a plain Arch Linux installation created according to:
> https://wiki.archlinux.org/index.php/Arch_systemd_container

OK, I fixed the crash, but this is incomplete as we really should
disallow multipl start requests on the same scope. I have added a TODO
list item for the latter now.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.