Comment 2 for bug 1242074

it was autostarted

Sent from my iPad

> On 20.10.2013, at 22:12, Serge Hallyn <email address hidden> wrote:
>
> Thanks for submitting this bug. Can you confirm whether the jenkins
> machine was auto-started by lxc-instance? If not, can you please
> run 'apport-collect 1242074' to have apport upload more information,
> and tell us the path and type of container, and how you created and started
> it?
>
> status: incomplete
>
>
> ** Changed in: lxc (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1242074
>
> Title:
> lxc-ls shows wrong status
>
> Status in “lxc” package in Ubuntu:
> Incomplete
>
> Bug description:
> I just upgraded to ubuntu saucy and found a strange behaviour. The
> command lxc-ls doesn't show the correct status of running machines.
>
> as you can see my output for jenkins is "stopped", but I am logged
> into the system (jenkins) at the very same moment, so it is running. I
> can also do thinks within the virtual machine, but the status doesn't
> change.
>
>
> # lxc-ls --fancy
> NAME STATE IPV4 IPV6 AUTOSTART
> -----------------------------------------
> jenkins STOPPED - - NO
> php-54-32 STOPPED - - NO
> test STOPPED - - NO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions