Provide ability to refresh IPs of machines

[Haw Loeung]

Hi,

For public clouds, when a VM is stopped and started, it is provisioned elsewhere and with a new IP address. Unfortunately, it can take some time for Juju to pick this up. It would be nice to have the ability to trigger a 'refresh' so it's picked up sooner rather than us waiting around running 'jsft' in a loop (we need to wait around to collect/update nagios monitoring checks).

| Machine State DNS Inst id Series AZ Message
| 0 down 52.231.69.128 machine-0 xenial

But in the Azure portal:

| Public IP address: 52.231.71.225

Unless this is not possible as Juju is waiting for the agents themselves to check in?

[John A Meinel (jameinel)]

I believe we have logic around how likely we think an IP address will be
changing and how long we should wait before polling that machine again.
We could potentially tie into that logic if a machine appears to be missing
(eg, if an agent transitions between reporting in and not reporting in and
vice-versa, put it in the 'should poll the provider right away'.)

On Tue, Oct 20, 2020 at 9:20 PM Haw Loeung <email address hidden>
wrote:

> Public bug reported:
>
> Hi,
>
> For public clouds, when a VM is stopped and started, it is provisioned
> elsewhere and with a new IP address. Unfortunately, it can take some
> time for Juju to pick this up. It would be nice to have the ability to
> trigger a 'refresh' so it's picked up sooner rather than us waiting
> around running 'jsft' in a loop (we need to wait around to
> collect/update nagios monitoring checks).
>
> | Machine State DNS Inst id Series AZ Message
> | 0 down 52.231.69.128 machine-0 xenial
>
> But in the Azure portal:
>
> | Public IP address: 52.231.71.225
>
> Unless this is not possible as Juju is waiting for the agents themselves
> to check in?
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> ** Description changed:
>
> Hi,
>
> For public clouds, when a VM is stopped and started, it is provisioned
> elsewhere and with a new IP address. Unfortunately, it can take some
> time for Juju to pick this up. It would be nice to have the ability to
> trigger a 'refresh' so it's picked up sooner rather than us waiting
> around running 'jsft' in a loop (we need to wait around to
> collect/update nagios monitoring checks).
> +
> + | Machine State DNS Inst id Series AZ Message
> + | 0 down 52.231.69.128 machine-0 xenial
> +
> + But in the Azure portal:
> +
> + | Public IP address: 52.231.71.225
> +
> + Unless this is not possible as Juju is waiting for the agents themselves
> + to check in?
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1900781
>
> Title:
> Provide ability to refresh IPs of machines
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1900781/+subscriptions
>

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.