add-unit should not assign a machine that is currently down
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
juju-core |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
As a follow up to bug #1205451, we can detect when a Machine agent is currently down. However, even if the agent is down, we'll still assign a Unit to it.
There are two things to consider:
1) If we just added the machine, we have every reason to expect the instance to come up, so we should assign the unit we started the machine for.
2) If we do: "juju add-machine; juju add-unit foo" should we use the machine we just added?
The idea from bug #1205451 is that if a machine was added, but then is killed (agent goes down), we probably don't want to assign anything to it, because it is reasonably likely to not come up again.
One option is that we can assign to a machine that is currently down as long as it has never showed as started.
tags: | added: 14.10 |
Changed in juju-core: | |
milestone: | none → next-stable |
tags: | added: cts |
Changed in juju-core: | |
milestone: | 1.21 → 1.22 |
Changed in juju-core: | |
milestone: | 1.22 → none |
importance: | High → Medium |
tags: |
added: sts removed: cts |
tags: | removed: cts-cloud-review sts |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 2.1.0 |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
Changed in juju: | |
importance: | Medium → High |
Changed in juju: | |
importance: | High → Medium |
milestone: | 2.1.0 → none |
This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.