Comment 14 for bug 1749201

Revision history for this message
Felipe Reyes (freyes) wrote :

I keep seeing this error in a freshly bootstrapped 2.3.6 environment

2018-04-20 20:51:46 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.6-xenial-amd64: open /var/lib/juju/tools/2.3.6-xenial-amd64/downloaded-tools.txt: no such file or directory

They way I'm upgrading the machine is this -> https://gist.github.com/freyes/5327cc554bd18d4f9f6059a9a1af153b

Full machine-5.log http://paste.ubuntu.com/p/qbjZPWr9Wt/

$ juju status -m controller
Model Controller Cloud/Region Version SLA
controller c2 stsstack/stsstack 2.3.6 unsupported

App Version Status Scale Charm Store Rev OS Notes

Unit Workload Agent Machine Public address Ports Message

Machine State DNS Inst id Series AZ Message
0 started 10.5.0.8 4e9c59cf-77bc-4525-a9dc-ab9b7345f612 xenial nova ACTIVE

$ snap info juju
name: juju
summary: juju client
publisher: canonical
contact: http://jujucharms.com
license: unknown
description: |
  Through the use of charms, juju provides you with shareable, re-usable, and repeatable expressions of
  devops best practices.
commands:
  - juju
snap-id: e2CPHpB1fUxcKtCyJTsm5t3hN9axJ0yj
tracking: stable
refreshed: 2018-04-18T13:14:30-03:00
installed: 2.3.6 (4108) 54MB classic
...
$ juju --version
2.3.6-bionic-amd64