juju deployed services to lxc containers stuck in pending
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Andrew Wilkins | ||
1.18 |
Fix Released
|
High
|
Andrew Wilkins |
Bug Description
Using juju 1.18, machines running trusty, deploying additional services to machines with lxc stay stuck in pending.
Looking at the one of the hosting machine logs (/var/log/
2014-05-07 16:34:28 INFO juju.cmd supercommand.go:302 running juju-1.
2014-05-07 16:34:28 INFO juju.cmd.jujud machine.go:127 machine agent machine-1 start (1.18.2-
2014-05-07 16:34:28 DEBUG juju.agent agent.go:384 read agent config, format "1.18"
2014-05-07 16:34:28 INFO juju runner.go:262 worker: start "api"
2014-05-07 16:34:28 INFO juju apiclient.go:114 state/api: dialing "wss://
2014-05-07 16:34:28 INFO juju runner.go:262 worker: start "termination"
2014-05-07 16:34:28 INFO juju apiclient.go:124 state/api: connection established
2014-05-07 16:34:28 DEBUG juju.agent agent.go:523 writing configuration file
2014-05-07 16:34:28 INFO juju runner.go:262 worker: start "upgrader"
2014-05-07 16:34:28 INFO juju runner.go:262 worker: start "upgrade-steps"
2014-05-07 16:34:28 INFO juju runner.go:262 worker: start "machiner"
2014-05-07 16:34:28 INFO juju.cmd.jujud machine.go:458 upgrade to 1.18.2-trusty-amd64 already completed.
2014-05-07 16:34:28 INFO juju.cmd.jujud machine.go:445 upgrade to 1.18.2-trusty-amd64 completed.
2014-05-07 16:34:28 INFO juju runner.go:262 worker: start "logger"
2014-05-07 16:34:28 DEBUG juju.worker.logger logger.go:35 initial log config: "<root>=DEBUG"
2014-05-07 16:34:28 INFO juju runner.go:262 worker: start "machineenviron
2014-05-07 16:34:28 INFO juju runner.go:262 worker: start "rsyslog"
2014-05-07 16:34:28 DEBUG juju.worker.logger logger.go:60 logger setup
2014-05-07 16:34:28 DEBUG juju.worker.
2014-05-07 16:34:28 DEBUG juju.worker.rsyslog worker.go:76 starting rsyslog worker mode 1 for "machine-1" ""
2014-05-07 16:34:28 INFO juju runner.go:262 worker: start "authentication
2014-05-07 16:34:28 DEBUG juju.worker.logger logger.go:45 reconfiguring logging from "<root>=DEBUG" to "<root>
2014-05-07 16:34:30 ERROR juju.utils.apt apt.go:133 apt-get command failed: exit status 100
args: []string{"apt-get", "--option=
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
2014-05-07 16:34:30 ERROR juju.provisioner container_
2014-05-07 16:34:30 ERROR juju runner.go:220 worker: exited "1-container-
Here's the juju status:
environment: oil-slave-1
machines:
"0":
agent-state: started
agent-version: 1.18.2
dns-name: lambert.oil
instance-id: /MAAS/api/
series: precise
"1":
agent-state: started
agent-version: 1.18.2
dns-name: reading.oil
instance-id: /MAAS/api/
series: trusty
containers:
1/lxc/0:
series: trusty
"2":
agent-state: started
agent-version: 1.18.2
dns-name: suangi.oil
instance-id: /MAAS/api/
series: trusty
containers:
2/lxc/0:
series: trusty
"3":
agent-state: started
agent-version: 1.18.2
dns-name: varaha.oil
instance-id: /MAAS/api/
series: trusty
containers:
3/lxc/0:
series: trusty
"4":
agent-state: started
agent-version: 1.18.2
dns-name: gulon.oil
instance-id: /MAAS/api/
series: trusty
containers:
4/lxc/0:
Related branches
- Juju Engineering: Pending requested
-
Diff: 285 lines (+78/-20)7 files modifiedcmd/jujud/agent.go (+10/-0)
cmd/jujud/machine.go (+5/-0)
cmd/jujud/unit.go (+6/-2)
worker/provisioner/container_initialisation.go (+15/-3)
worker/provisioner/container_initialisation_test.go (+34/-6)
worker/uniter/uniter.go (+4/-8)
worker/uniter/uniter_test.go (+4/-1)
- Juju Engineering: Pending requested
-
Diff: 317 lines (+82/-25)7 files modifiedcmd/jujud/agent.go (+10/-0)
cmd/jujud/machine.go (+9/-5)
cmd/jujud/unit.go (+6/-2)
worker/provisioner/container_initialisation.go (+15/-3)
worker/provisioner/container_initialisation_test.go (+34/-6)
worker/uniter/uniter.go (+4/-8)
worker/uniter/uniter_test.go (+4/-1)
Changed in juju-core: | |
milestone: | 1.18.3 → 1.18.4 |
Changed in juju-core: | |
status: | Triaged → In Progress |
assignee: | nobody → Andrew Wilkins (axwalk) |
Changed in juju-core: | |
milestone: | 1.18.4 → 1.19.3 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
tags: | added: landscape |
I would have thought this would be a dupe of bug #1302820 or bug #1311676
but both of those were considered fixed in 1.18.2 which it appears you are
using.
Which would indicate we have another bug hiding out for multiple-series
support.
On Wed, May 7, 2014 at 9:05 PM, Ryan Harper <email address hidden>wrote:
> Public bug reported: juju/machine- 2.log), lxc packages fail to install with: 18.2-trusty- amd64 [gc] trusty- amd64 [gc]) 0.185:17070/ " mentworker" machineenvironm ent entworker. go:70 write system files: true worker" =WARNING; unit=DEBUG" Dpkg::Options: :=--force- confold" , Dpkg::options: :=--force- unsafe- io", "--assume-yes", "--quiet", image-utils" } initialisation. go:90
>
> Using juju 1.18, machines running trusty, deploying additional services to
> machines with lxc stay stuck in pending.
> Looking at the one of the hosting machine logs
> (/var/log/
>
> 2014-05-07 16:34:28 INFO juju.cmd supercommand.go:302 running
> juju-1.
> 2014-05-07 16:34:28 INFO juju.cmd.jujud machine.go:127 machine agent
> machine-1 start (1.18.2-
> 2014-05-07 16:34:28 DEBUG juju.agent agent.go:384 read agent config,
> format "1.18"
> 2014-05-07 16:34:28 INFO juju runner.go:262 worker: start "api"
> 2014-05-07 16:34:28 INFO juju apiclient.go:114 state/api: dialing "wss://
> 10.245.
> 2014-05-07 16:34:28 INFO juju runner.go:262 worker: start "termination"
> 2014-05-07 16:34:28 INFO juju apiclient.go:124 state/api: connection
> established
> 2014-05-07 16:34:28 DEBUG juju.agent agent.go:523 writing configuration
> file
> 2014-05-07 16:34:28 INFO juju runner.go:262 worker: start "upgrader"
> 2014-05-07 16:34:28 INFO juju runner.go:262 worker: start "upgrade-steps"
> 2014-05-07 16:34:28 INFO juju runner.go:262 worker: start "machiner"
> 2014-05-07 16:34:28 INFO juju.cmd.jujud machine.go:458 upgrade to
> 1.18.2-trusty-amd64 already completed.
> 2014-05-07 16:34:28 INFO juju.cmd.jujud machine.go:445 upgrade to
> 1.18.2-trusty-amd64 completed.
> 2014-05-07 16:34:28 INFO juju runner.go:262 worker: start "logger"
> 2014-05-07 16:34:28 DEBUG juju.worker.logger logger.go:35 initial log
> config: "<root>=DEBUG"
> 2014-05-07 16:34:28 INFO juju runner.go:262 worker: start
> "machineenviron
> 2014-05-07 16:34:28 INFO juju runner.go:262 worker: start "rsyslog"
> 2014-05-07 16:34:28 DEBUG juju.worker.logger logger.go:60 logger setup
> 2014-05-07 16:34:28 DEBUG juju.worker.
> machineenvironm
> 2014-05-07 16:34:28 DEBUG juju.worker.rsyslog worker.go:76 starting
> rsyslog worker mode 1 for "machine-1" ""
> 2014-05-07 16:34:28 INFO juju runner.go:262 worker: start
> "authentication
> 2014-05-07 16:34:28 DEBUG juju.worker.logger logger.go:45 reconfiguring
> logging from "<root>=DEBUG" to "<root>
> 2014-05-07 16:34:30 ERROR juju.utils.apt apt.go:133 apt-get command
> failed: exit status 100
> args: []string{"apt-get", "--option=
> "--option=
> "install", "lxc", "cloud-
> E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily
> unavailable)
> E: Unable to lock the administration directory (/var/lib/dpkg/), is
> another process using it?
>
> 2014-05-07 16:34:30 ERROR juju.provisioner container_
> starting container provisioner for lxc: setting up container dependnecies
> on host...