Address changes should be propagated to relations

Bug #1215579 reported by Kapil Thangavelu
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
Medium
Unassigned

Bug Description

If a machine is restarted, the units on the machine should record their current address when starting up *and* propogate that to all their relations so that the unit connections can be re-established. Currently the 'private-address' key is seeded by juju and thus juju has the responsibility for maintaining it.

Revision history for this message
John A Meinel (jameinel) wrote :

I think this falls into what Martin is working on with addressibility. I'm not sure if it is a duplicate of something that he's already been working on. But handling IP address changes is definitely part of that work. (Assigning a new public IP is another way this can happen even without the machine restarting.)

Changed in juju-core:
importance: Undecided → High
status: New → Triaged
Curtis Hovey (sinzui)
tags: added: adressability
Curtis Hovey (sinzui)
tags: added: addressability
removed: adressability
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: none → next-stable
Curtis Hovey (sinzui)
tags: added: reliability
Revision history for this message
Kapil Thangavelu (hazmat) wrote :
Revision history for this message
Kapil Thangavelu (hazmat) wrote : Re: [Bug 1215579] Re: Address changes should be propagated to relations

Workaround posted to https://gist.github.com/kapilt/a61efcb4eaef9e685397

On Mon, May 26, 2014 at 8:34 PM, Kapil Thangavelu <
<email address hidden>> wrote:

> Example of this biting a user https://bugs.launchpad.net/juju-
> core/+bug/1256053/comments/3
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1215579
>
> Title:
> Address changes should be propagated to relations
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1215579/+subscriptions
>

Andrew Wilkins (axwalk)
Changed in juju-core:
status: Triaged → In Progress
assignee: nobody → Andrew Wilkins (axwalk)
Andrew Wilkins (axwalk)
Changed in juju-core:
assignee: Andrew Wilkins (axwalk) → nobody
status: In Progress → Triaged
Andrew Wilkins (axwalk)
Changed in juju-core:
status: Triaged → In Progress
assignee: nobody → Andrew Wilkins (axwalk)
Revision history for this message
Thiago Bellini (bellini666) wrote :

Kapil: Thank you so much for the workaround! Worked great.

I just had to fix a little problem on the gist. Those fixes are on a gist fork and you can pull them to yours :)

Changed in juju-core:
assignee: Andrew Wilkins (axwalk) → nobody
status: In Progress → Triaged
Curtis Hovey (sinzui)
Changed in juju-core:
importance: High → Medium
milestone: next-stable → none
Revision history for this message
Kapil Thangavelu (hazmat) wrote :

This is probably the most serious correctness bug with juju i can think of. its advertising invalid data and state of reality to services and units.

Changed in juju-core:
importance: Medium → High
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: none → 1.22
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 1.22 → 1.23
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 1.23 → none
importance: High → Medium
tags: added: network
Revision history for this message
Dimiter Naydenov (dimitern) wrote :

This is fixed for quite some time now - config-changed hook gets fired when either the config or the addresses of the unit have changed.

Changed in juju-core:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.