This has been seen on more than api-controller-rename.
If you try to add-machine immediately after the bootstrap of the manual provider, you will get this connection is shut down error. I image it would happen with any command.
Running the command again will succeed.
Initial investigation shows that the mongo connection drops right after bootstrap completes. I see these messages in /var/log/syslog at the time that the connection drops: http://paste.ubuntu.com/14698112/
Seems to happen at the same time as this line in machine-0.log:
2016-01-29 19:33:24 DEBUG juju.replicaset replicaset.go:168 Set() changing replica set
Which is followed by:
2016-01-29 19:33:24 DEBUG juju.replicaset replicaset.go:179 got EOF while running Set(), calling session.Refresh()
I see the same messages in machine-0.log and /var/log/syslog when I bootstrap my MAAS env, but the timing is different such that running `juju bootstrap && juju add-machine` will succeed.
This has been seen on more than api-controller- rename.
If you try to add-machine immediately after the bootstrap of the manual provider, you will get this connection is shut down error. I image it would happen with any command.
Running the command again will succeed.
Initial investigation shows that the mongo connection drops right after bootstrap completes. I see these messages in /var/log/syslog at the time that the connection drops: http:// paste.ubuntu. com/14698112/
Seems to happen at the same time as this line in machine-0.log:
2016-01-29 19:33:24 DEBUG juju.replicaset replicaset.go:168 Set() changing replica set
Which is followed by:
2016-01-29 19:33:24 DEBUG juju.replicaset replicaset.go:179 got EOF while running Set(), calling session.Refresh()
I see the same messages in machine-0.log and /var/log/syslog when I bootstrap my MAAS env, but the timing is different such that running `juju bootstrap && juju add-machine` will succeed.