2018-02-13 14:35:11 DEBUG juju.worker.dependency engine.go:486 "unit-agent-deployer" manifold worker started
2018-02-13 14:35:11 DEBUG juju.service discovery.go:63 discovered init system "systemd" from series "xenial"
2018-02-13 14:35:12 INFO juju.worker.deployer deployer.go:115 checking unit "ubuntu/0"
2018-02-13 14:35:12 INFO juju.worker.deployer deployer.go:158 deploying unit "ubuntu/0"
2018-02-13 14:35:12 DEBUG juju.service discovery.go:111 failed to find init system "upstart": exec "/sbin/initctl" failed: exit status 1
2018-02-13 14:35:12 DEBUG juju.service discovery.go:115 discovered init system "systemd" from local host
2018-02-13 14:35:12 DEBUG juju.worker.dependency engine.go:504 "unit-agent-deployer" manifold worker stopped: cannot read agent metadata in directory /var/lib/juju/tools/2.3.2-xenial-amd64: open /var/lib/juju/tools/2.3.2-xenial-amd64/downloaded-tools.txt: no such file or directory
2018-02-13 14:35:12 ERROR juju.worker.dependency engine.go:551 "unit-agent-deployer" manifold worker returned unexpected error: cannot read agent metadata in directory /var/lib/juju/tools/2.3.2-xenial-amd64: open /var/lib/juju/tools/2.3.2-xenial-amd64/downloaded-tools.txt: no such file or directory
2018-02-13 14:35:12 DEBUG juju.worker.dependency engine.go:553 stack trace:
cannot read agent metadata in directory /var/lib/juju/tools/2.3.2-xenial-amd64: open /var/lib/juju/tools/2.3.2-xenial-amd64/downloaded-tools.txt: no such file or directory
github.com/juju/juju/worker/deployer/simple.go:127:
On the unit in question, we can see the trusty tools but not xenial ones:
ubuntu@juju-cf2ccb-0:~$ ls /var/lib/juju/tools/2.3.2-trusty-amd64/downloaded-tools.txt
/var/lib/juju/tools/2.3.2-trusty-amd64/downloaded-tools.txt
ubuntu@juju-cf2ccb-0:~$ ls /var/lib/juju/tools/2.3.2-xenial-amd64/downloaded-tools.txt
ls: cannot access '/var/lib/juju/tools/2.3.2-xenial-amd64/downloaded-tools.txt': No such file or directory
@chris.macnaughton, did you try a reboot?
This is a doc bug, because the instructions (https:/ /jujucharms. com/docs/ stable/ howto-updateser ies) were incorrect. There is no expectation that the 'juju update-series' command will make changes on existing units itself.