juju 1.20 consistently fails to bootstrap a MAAS environment (regression from 1.18)
Bug #1339240 reported by
James Troup
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Andrew Wilkins | ||
1.20 |
Fix Released
|
Critical
|
Andrew Wilkins |
Bug Description
I'm using juju 1.20.0-
on Ubuntu 14.04 with MAAS 1.5.2+bzr2282-
bootstrap an environment, it fails reproducibly (3 times and across different
hardware) with the following message:
2014-07-08 17:16:51 INFO juju.worker.
2014-07-08 17:16:51 ERROR juju.cmd supercommand.go:323 cannot initiate replica set: Closed explicitly
Full log:
https:/
I was previously able to successfully bootstrap an environment with
this MAAS with juju 1.18.1-0ubuntu1 from trusty directly.
Changed in juju-core: | |
importance: | Undecided → Critical |
status: | New → Triaged |
Changed in juju-core: | |
milestone: | none → 1.21-alpha1 |
Changed in juju-core: | |
assignee: | nobody → Andrew Wilkins (axwalk) |
status: | Triaged → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → In Progress |
status: | In Progress → Fix Committed |
tags: | added: landscape |
tags: | added: oil |
tags: | added: regression |
Changed in juju-core: | |
importance: | Critical → High |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
So, just to confirm, I ran this a fourth time with 1.20 and it failed again. I downgraded to 1.18 and it bootstrapped just fine.