Juju2 with MAAS2, log shows errors after having created a controller
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Expired
|
Undecided
|
Unassigned |
Bug Description
On a fresh Xenial system I am using Juju 2.0 and MAAS 2.0. After creating a controller, which seemed to go fine, I am getting errors in the logs. Both Juju and MAAS are on the same host. The MAAS nodes (the one used for the controller) is a KVM guest on another system.
Juju client: 192.168.1.5
MAAS server: 192.168.1.5
Juju controller: 192.168.1.64
$ export JUJU_DEV_
$ juju bootstrap --bootstrap-
$ juju list-controllers
CONTROLLER MODEL USER CLOUD/REGION
local.maas-
$ juju show-controller maas-controller
=======
maas-controller:
details:
uuid: b3073ded-
api-endpoints: ['192.168.
ca-cert: |
-----BEGIN CERTIFICATE-----
MIID0zCCA
BQAwcTENM
Zm9yIG1vZ
ZDQyLTg1M
MzIwOVowc
Q0EgZm9yI
MS00ZDQyL
MIIBCgKCA
fg+
fuA8oU+
I9MoKXAVf
rZn/
snoPOOF/
AqQwDwYDV
i+
BQADggEBA
zK3Ec1U7S
PQMH8ThVx
KIbnuOpq/
NrZju2r6i
3mOwVK55F
-----END CERTIFICATE-----
cloud: golem-maas
accounts:
admin@local:
user: admin@local
models:
controller:
uuid: b3073ded-
default:
uuid: ff5a5833-
current-
current-account: admin@local
bootstrap-config:
cloud: golem-maas
cloud-type: maas
endpoint: http://
credential: golem
=======
$ juju switch
local.maas-
$ juju debug-log --replay -T -l TRACE | grep ERROR
machine-0: 2016-06-13 20:42:14 ERROR juju.worker.
del/b3073ded-
machine-0: 2016-06-13 20:42:18 ERROR juju.api.watcher watcher.go:86 error trying to stop watcher: connection is shut down
machine-0: 2016-06-13 20:42:18 ERROR juju.api.watcher watcher.go:86 error trying to stop watcher: connection is shut down
machine-0: 2016-06-13 20:42:18 ERROR juju.api.watcher watcher.go:86 error trying to stop watcher: connection is shut down
machine-0: 2016-06-13 20:42:18 ERROR juju.api.watcher watcher.go:86 error trying to stop watcher: connection is shut down
machine-0: 2016-06-13 20:42:18 ERROR juju.api.watcher watcher.go:86 error trying to stop watcher: connection is shut down
machine-0: 2016-06-13 20:42:18 ERROR juju.worker.logger logger.go:47 connection is shut down
machine-0: 2016-06-13 20:42:18 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:42:18 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:42:18 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:42:18 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:42:18 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:42:18 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:42:18 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:42:18 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:42:18 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:42:18 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:42:18 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:42:18 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:42:18 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:42:18 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:42:18 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:42:18 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:42:21 ERROR juju.rpc server.go:577 error writing response: write tcp 127.0.0.
machine-0: 2016-06-13 20:54:12 ERROR juju.apiserver.
-50c69234dcf8:
description: | updated |
Here is /var/log/syslog from the controller:
http:// paste.ubuntu. com/17311172/