Comment 6 for bug 1613992

juju agent-version: 1.25.6, service status message: Waiting for agent initialization to finish

This problem is not related to any specific charm. We hit it with 3 different charms. The problem arises when we try to remove a successfully deployed service and redeploy a modified one. Our environment is latest xenial and latest juju. It happens on both arm aarch64 and intel xeon.

The juju server version 1.25.0-trusty-amd64 is different from juju agent-version: 1.25.6

We will try to use --no-auto-upgrade to bootstrap environment again.

logs:
unit-ngi4-0[13689]: 2016-09-16 21:32:31 WARNING juju.worker.uniter.operation leader.go:115 we should run a leader-deposed hook here, but we can't yet
unit-ngi4-0[13689]: 2016-09-16 21:32:33 WARNING juju.worker.uniter.operation metrics.go:50 failed to create a metric reader: failed to open spool directory "/var/lib/juju/agents/unit-ngi4-0/state/spool/metrics": stat /var/lib/juju/agents/unit-ngi4-0/state/spool/metrics: no such file or directory
unit-ngi4-0[13689]: 2016-09-16 21:32:33 ERROR juju.worker.uniter.filter filter.go:137 tomb: dying
unit-ngi4-0[13689]: 2016-09-16 21:32:33 ERROR juju.api.watcher watcher.go:84 error trying to stop watcher: crypto/tls: use of closed connection
unit-ngi4-0[13689]: 2016-09-16 21:32:33 ERROR juju.api.watcher watcher.go:84 error trying to stop watcher: connection is shut down
unit-ngi4-0[13689]: 2016-09-16 21:32:33 ERROR juju.worker runner.go:212 fatal "api": agent should be terminated
unit-ngi4-0[13689]: message repeated 5 times: [ 2016-09-16 21:32:33 ERROR juju.api.watcher watcher.go:84 error trying to stop watcher: connection is shut down]
machine-0: message repeated 5 times: [2016-09-16 21:30:38 ERROR juju.rpc server.go:573 error writing response: write tcp 10.118.zzz.xxx:17070->10.118.zzz.aaa:49670: write: connection reset by peer]
machine-0: 2016-09-16 21:32:33 ERROR juju.rpc server.go:573 error writing response: write tcp 10.118.zzz.xxx:17070->10.118.zzz.bbb:36298: write: broken pipe