cached unit public addresses are problematic when public ip address changes

Bug #928624 reported by Kapil Thangavelu
60
This bug affects 11 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
Medium
Unassigned
juju-core
Won't Fix
Medium
Unassigned
pyjuju
Won't Fix
Low
Unassigned

Bug Description

in ec2 or openstack associating an elastic ip changes the unit's public address. At minimum, things with access to the provider should like juju ssh/debug-hooks should resolve the unit's current public address.

Changed in juju:
status: New → Confirmed
importance: Undecided → Medium
milestone: none → florence
Changed in juju:
milestone: florence → galapagos
Changed in juju:
milestone: galapagos → honolulu
Changed in juju:
milestone: 0.6 → none
tags: added: canonical-webops-juju
Changed in juju:
milestone: none → 0.8
Curtis Hovey (sinzui)
Changed in juju:
status: Confirmed → Triaged
Revision history for this message
Kapil Thangavelu (hazmat) wrote : Re: [Bug 928624] Re: cached unit public addresses are problematic when public ip address changes

juju-core supports restarts to get new addresses recorded, but does not
support runtime changes,or propogration of address changes to relations.

On Fri, Oct 11, 2013 at 11:42 PM, Curtis Hovey <email address hidden> wrote:

> ** Changed in: juju
> Status: Confirmed => Triaged
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/928624
>
> Title:
> cached unit public addresses are problematic when public ip address
> changes
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/928624/+subscriptions
>

Curtis Hovey (sinzui)
Changed in juju:
importance: Medium → Low
Revision history for this message
Curtis Hovey (sinzui) wrote :

This bug is a somewhat inverse to bug 1248674 where the bootstrap node's IP address changes.

tags: added: addressability
Changed in juju-core:
importance: Undecided → High
status: New → Triaged
Mark Ramm (mark-ramm)
Changed in juju:
status: Triaged → Won't Fix
Changed in juju-core:
status: Triaged → Confirmed
status: Confirmed → Won't Fix
milestone: none → 2.0
Mark Ramm (mark-ramm)
Changed in juju-core:
status: Won't Fix → Triaged
Ryan Finnie (fo0bar)
tags: added: canonical-is
Changed in juju-core:
importance: High → Medium
tags: added: network
Changed in juju:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 2.1.0
Changed in juju-core:
status: Triaged → Won't Fix
Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.1-rc2 → none
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

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.

Changed in juju:
status: Triaged → Expired
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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