Deployments during an HA transition get stuck
Bug #1620067 reported by
Mark Shuttleworth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned |
Bug Description
I have been hammering a little on our HA support, and have observed that doing a large bundle deployment while at the same time nuking the active Juju endpoint results in stuck machines. The machines boot but the agent never becomes available. I suspect that the machines booting get told a simplistic version of where the controller is, and if the controller moves while they are booting they have no way to figure out where to register themselves. But that's a guess.
I think the summary of this bug is 'lets review the machine bringup process and ensure it is bulletproof even if the controller is losing nodes during the bringup'.
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in juju: | |
milestone: | none → 2.0-rc1 |
Changed in juju: | |
milestone: | 2.0-rc1 → 2.0-rc2 |
Changed in juju: | |
milestone: | 2.0-rc2 → 2.0.0 |
assignee: | nobody → Alexis Bruemmer (alexis-bruemmer) |
tags: | added: ha |
tags: | added: ateam |
Changed in juju: | |
milestone: | 2.0-rc3 → 2.0.0 |
Changed in juju: | |
assignee: | Alexis Bruemmer (alexis-bruemmer) → Menno Smits (menno.smits) |
Changed in juju: | |
milestone: | 2.0.0 → 2.0.1 |
Changed in juju: | |
milestone: | 2.0.1 → none |
Changed in juju: | |
milestone: | none → 2.2.0 |
Changed in juju: | |
milestone: | 2.2-beta1 → 2.2-beta2 |
Changed in juju: | |
milestone: | 2.2-beta2 → 2.2-beta3 |
Changed in juju: | |
milestone: | 2.2-beta3 → 2.2-beta4 |
Changed in juju: | |
milestone: | 2.2-beta4 → 2.2-rc1 |
Changed in juju: | |
assignee: | Menno Finlay-Smits (menno.smits) → nobody |
To post a comment you must log in.
We have some provisioner related cleanup targetted for 2.3. Instead of punting this each release, we'll assign a milestone when work has started on it.