Juju bootstrap fails with nonce mis-match error

Bug #1469844 reported by John George
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
Medium
Unassigned

Bug Description

Logs can be seen here:

Master:
http://reports.vapour.ws/releases/2823/job/maas-upgrade-trusty-amd64/attempt/998

devices-api-maas:
http://reports.vapour.ws/releases/2824/job/maas-upgrade-trusty-amd64/attempt/1001

feature-proc-mgmt:
http://reports.vapour.ws/releases/2825/job/maas-upgrade-trusty-amd64/attempt/1004

Launching instance
 - /MAAS/api/1.0/nodes/node-0e2eb068-ed18-11e4-a40e-525400c43ce5/
2015-06-27 05:36:45 INFO juju.environs.bootstrap bootstrap.go:184 newest version: 1.24.0
2015-06-27 05:36:45 INFO juju.environs.bootstrap bootstrap.go:212 picked bootstrap tools version: 1.24.0
Installing Juju agent on bootstrap instance
Waiting for address
Attempting to connect to juju-qa-maas-node-27.maas:22
Attempting to connect to juju-qa-maas-node-27.maas:22
Attempting to connect to 10.0.30.180:22
2015-06-27 05:46:45 ERROR juju.cmd supercommand.go:430 failed to bootstrap environment: waited for 10m0s without being able to connect: Warning: Permanently added '10.0.30.180' (ECDSA) to the list of known hosts.
/var/lib/juju/nonce.txt contents do not match machine nonce

John George (jog)
tags: added: bootstrap ci intermittent-failure maas-provider
John George (jog)
Changed in juju-core:
importance: Undecided → Medium
status: New → Triaged
Curtis Hovey (sinzui)
Changed in juju-core:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.