juju-core

template container did not stop

Bug #1320121 reported by Stuart Bishop
This bug report is a duplicate of:  Bug #1348386: lxc template fails to stop. Edit Remove
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core
Triaged
Medium
Unassigned

Bug Description

I am using the local provider with juju 1.18.1-trusty-amd64. I destroyed my environment, and removed my juju-precise-template and juju-trusty-template lxc containers.

'juju bootstrap' works fine. However, deploying my first service with 'juju deploy ubuntu' fails and hangs in a pending state, with the machine reporting agent-state-info: '(error: template container "juju-precise-template" did not stop)'.

Checking 'lxc-ls --fancy', I see that the juju-precise-template container is in a stopped state.

Deploying a second service works just fine.

Destroying the environment and bootstrapping again, without trashing the juju-precise-template container, everything also works fine.

Revision history for this message
Curtis Hovey (sinzui) wrote :

I believe juju creates its own locks (in the form of directories?). abentley reported that the his services were stuck in pending because of stale locks. Could stale locks be a factor in this bug?

Changed in juju-core:
status: New → Triaged
importance: Undecided → Medium
tags: added: local-provider lxc
tags: added: deploy
Revision history for this message
Ian Booth (wallyworld) wrote :

I believe this bug may actually be a duplicate of bug 1348386.
The template container is not recognised as stopped because the console log is not available.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.