cannot get tools from machine for lxc container

[Ryan Harper]

  "5":
    agent-state: started
    agent-version: 1.20.5
    dns-name: puritan.oil
    instance-id: /MAAS/api/1.0/nodes/node-f7aa0d6e-f8b8-11e3-9f8c-00163eca07b6/
    series: trusty
    containers:
      5/lxc/0:
        instance-id: pending
        series: trusty

2014-08-20 22:06:06 INFO juju.cmd supercommand.go:37 running jujud [1.20.5-trusty-amd64 gc]
2014-08-20 22:06:06 INFO juju.cmd.jujud machine.go:156 machine agent machine-5 start (1.20.5-trusty-amd64 [gc])
2014-08-20 22:06:06 DEBUG juju.agent agent.go:377 read agent config, format "1.18"
2014-08-20 22:06:06 INFO juju.worker runner.go:260 start "api"
2014-08-20 22:06:06 INFO juju.worker runner.go:260 start "statestarter"
2014-08-20 22:06:06 INFO juju.worker runner.go:260 start "termination"
2014-08-20 22:06:06 INFO juju.state.api apiclient.go:242 dialing "wss://hayward-12.oil:17070/"
2014-08-20 22:06:06 INFO juju.state.api apiclient.go:176 connection established to "wss://hayward-12.oil:17070/"
2014-08-20 22:06:06 INFO juju.state.api apiclient.go:242 dialing "wss://hayward-12.oil:17070/"
2014-08-20 22:06:06 INFO juju.state.api apiclient.go:176 connection established to "wss://hayward-12.oil:17070/"
2014-08-20 22:06:07 INFO juju.state.api apiclient.go:242 dialing "wss://hayward-12.oil:17070/"
2014-08-20 22:06:07 INFO juju.state.api apiclient.go:176 connection established to "wss://hayward-12.oil:17070/"
2014-08-20 22:06:07 INFO juju.worker runner.go:260 start "upgrader"
2014-08-20 22:06:07 INFO juju.worker runner.go:260 start "upgrade-steps"
2014-08-20 22:06:07 INFO juju.worker runner.go:260 start "machiner"
2014-08-20 22:06:07 INFO juju.cmd.jujud machine.go:800 upgrade to 1.20.5-trusty-amd64 already completed.
2014-08-20 22:06:07 INFO juju.cmd.jujud machine.go:781 upgrade to 1.20.5-trusty-amd64 completed.
2014-08-20 22:06:07 INFO juju.worker runner.go:260 start "apiaddressupdater"
2014-08-20 22:06:07 INFO juju.worker runner.go:260 start "logger"
2014-08-20 22:06:07 INFO juju.worker runner.go:260 start "machineenvironmentworker"
2014-08-20 22:06:07 DEBUG juju.worker.logger logger.go:35 initial log config: "<root>=DEBUG"
2014-08-20 22:06:07 DEBUG juju.worker.machineenvironment machineenvironmentworker.go:71 write system files: true
2014-08-20 22:06:07 DEBUG juju.worker.logger logger.go:60 logger setup
2014-08-20 22:06:07 INFO juju.worker runner.go:260 start "rsyslog"
2014-08-20 22:06:07 DEBUG juju.worker.rsyslog worker.go:75 starting rsyslog worker mode 1 for "machine-5" ""
2014-08-20 22:06:07 INFO juju.worker runner.go:260 start "authenticationworker"
2014-08-20 22:06:07 DEBUG juju.worker.logger logger.go:45 reconfiguring logging from "<root>=DEBUG" to "<root>=WARNING;unit=DEBUG"
2014-08-20 22:06:07 INFO juju.worker.machiner machiner.go:86 setting addresses for machine-5 to ["local-machine:127.0.0.1" "local-cloud:10.245.0.107" "local-machine:::1" "fe80::2e59:e5ff:fe41:dc28"]
2014-08-20 22:06:07 ERROR juju.provisioner container_initialisation.go:154 cannot get tools from machine for lxc container
2014-08-20 22:06:07 ERROR juju.provisioner container_initialisation.go:95 starting container provisioner for lxc: initialising container infrastructure on host machine: agent tools for machine 5 not found
2014-08-20 22:06:07 ERROR juju.worker runner.go:218 exited "5-container-watcher": initialising container infrastructure on host machine: agent tools for machine 5 not found

[Ian Booth (wallyworld)]

Can you please provide some more information about how this error occurred? What were the juju commands that were issued? Were the lxc containers running on bare metal or kvm? Can you attach the entire all-machines.log file? Can we please see a full juju status output?

[Ian Booth (wallyworld)]

Also, was this system upgraded or deployed initially as 1.20.5?

[Curtis Hovey (sinzui)]

I see the number 5. Is this a manifestation the 5th container fails?

[Ian Booth (wallyworld)]

This bug is not a dup of 1350008. The issue here is that when the machine agent starts on the container, it tries to read the version of tools set on on the host machine and fails because this attribute has not been set yet.

[Ian Booth (wallyworld)]

It looks like there's a potential problem with start up of workers - the worker to set up container support on a host machine might attempt to read the tools version available on that machine before the information has been written out.

[Ryan Harper (raharper)]

When does this hit the juju-stable ppa then? Or is there another way to
test this fix out ?

On Thu, Aug 28, 2014 at 4:20 PM, Aaron Bentley <email address hidden>
wrote:

> ** Changed in: juju-core/1.20
> Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1359800
>
> Title:
> cannot get tools from machine for lxc container
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1359800/+subscriptions
>