manual: race condition on bootstrap machine addresses
Bug #1314430 reported by
Andrew Wilkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| juju-core | ||||||
| 1.18 |
Fix Released
|
High
|
Andrew Wilkins | |||
Bug Description
We currently do not set the bootstrap machine's addresses at bootstrap time, relying instead on instancepoller (which no longer does anything for manual) and the machiner (which takes addresses from all interfaces).
This can cause an error where the provisioner errors because the state server does not have any addresses.
Related branches
lp:~axwalk/juju-core/lp1314430-bootstrap-machine-addresses-1.18
- Juju Engineering: Pending requested
-
Diff: 262 lines (+97/-17)4 files modifiedagent/bootstrap.go (+4/-0)
agent/bootstrap_test.go (+3/-0)
cmd/jujud/bootstrap.go (+17/-0)
cmd/jujud/bootstrap_test.go (+73/-17)
Revision history for this message
| Andrew Wilkins (axwalk) wrote | #1 |
| no longer affects: | juju-core/trunk |
| no longer affects: | juju-core |
To post a comment you must log in.
I've investigated a bit more, and I can see that this is a problem only for 1.18, and not trunk. For 1.18 we made some unrelated changes to the bootstrap procedure that means that the bootstrap machine is always initialised with addresses. This was done in relation to HA, so it is not present in 1.18.