private-address isn't updated on machine reboot
Bug #1606922 reported by
Marco Ceppi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
High
|
Unassigned | ||
Bug Description
A few times I've had to scale application units UP in amazon by shutting them down, changing instance type, then booting them up again.
While the public-address change is picked up by Juju (very nice) the private address change isn't which means the relationships bucket "private-address" doesn't get updated which means relation-changed won't fire resulting in a broken deployment.
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.0.0 |
| tags: | added: silph-road |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0.0 → none |
| milestone: | none → 2.0.0 |
Revision history for this message
| Richard Harding (rharding) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Incomplete |
| Changed in juju: | |
| milestone: | 2.0-rc3 → 2.0.0 |
| Changed in juju: | |
| milestone: | 2.0.0 → none |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in juju: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
Can you test this with b17 please? We recently did some changes around this and if it's still an issue I'd like to make sure we get this specifically addressed before RC.