juju 2.0-beta12 ERROR unable to contact api server after 61 attempts: upgrade in progress (upgrade in progress)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
New
|
Undecided
|
Unassigned |
Bug Description
I have an environment which consists of 3 VMs registered in MAAS that I have been using since approximately 2.0-beta7, and since I upgraded to beta12 in the bootstrap process I'm getting the following error:
$ juju bootstrap --keep-broken --upload-tools --no-gui --constraints tags=bootstrap mymaas mymaas
Creating Juju controller "mymaas" on mymaas
Bootstrapping model "controller"
Starting new instance for initial controller
Launching instance
WARNING no architecture was specified, acquiring an arbitrary node
- 4y3h7s
Building tools to upload (2.0-beta12.
Installing Juju agent on bootstrap instance
Juju GUI installation has been disabled
Waiting for address
Attempting to connect to 192.168.30.3:22
Attempting to connect to fd39:6c94:
@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:
Please contact your system administrator.
Add correct host key in /home/ubuntu/
Offending ECDSA key in /home/ubuntu/
remove with:
ssh-keygen -f "/home/
Keyboard-
Logging to /var/log/
Running apt-get update
Running apt-get upgrade
Installing package: curl
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: cloud-utils
Installing package: cloud-image-utils
Installing package: tmux
Bootstrapping Juju machine agent
Starting Juju machine agent (jujud-machine-0)
Bootstrap agent installed
Waiting for API to become available: upgrade in progress (upgrade in progress)
[...]
Waiting for API to become available: upgrade in progress (upgrade in progress)
ERROR unable to contact api server after 61 attempts: upgrade in progress (upgrade in progress)
Probably this is race condition that my env is triggering, because I could successfully deploy once.
In the machine-0.log ( http://
Also inspecting /var/log/syslog I found a "exception: E11000 duplicate key error collection" error[0], but I'm not sure if this is something that juju internally manages properly or not.
[Other info]
* juju-2.0, version: 2.0-beta12~
* attaching /var/log/ directory from the controller node.
[0] Jul 21 14:55:22 ubuntu mongod.37017[5332]: [conn22] command juju.ip.addresses command: insert { insert: "ip.addresses", documents: [ { _id: "f77a530a-
I've been battling with the E11000 error a bunch, can you try the binaries from https:/ /bugs.launchpad .net/juju- core/+bug/ 1604644/ comments/ 11
I haven't run into this issue with those, make sure to use --upload-tools