RFC1918 IPs in public address in AWS after 2.9.32 upgrade
Bug #1980731 reported by
Gareth Woolridge
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Won't Fix
|
Undecided
|
Heather Lanigan |
Bug Description
We recently upgraded a controller and models in AWS from 2.9.18 to 2.9.32.
Following the upgrade the "Public address" for applications deployed in the one real model for this controller switched from showing actual public cloud IPs to internal RFC1918 instance networkig IPs.
This has broken our monitoring as it caused us to register unroutable from our company network RFC1918 address into prometheus.
We have upgraded about 6 of our AWS controllers (all hosting similar applications) and this is the only model/controller (so far) showing this behaviour.
I've attached a broken and none broken juju status as examples.
tags: | added: canonical-is-upgrades |
To post a comment you must log in.
Can you also include `juju status --format=yaml` which should include all
addresses that we know about a machine, and not just a single 'best'
address to give.
It does look incorrect, though.
On Tue, Jul 5, 2022 at 6:30 AM Tom Haddon <email address hidden>
wrote:
> ** Tags added: canonical- is-upgrades /bugs.launchpad .net/bugs/ 1980731 /bugs.launchpad .net/juju/ +bug/1980731/ +subscriptions
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> RFC1918 IPs in public address in AWS after 2.9.32 upgrade
>
> To manage notifications about this bug go to:
> https:/
>
>