Comment 13 for bug 1761838
Revision history for this message
| Erik Lönroth (erik-lonroth) wrote Re: [Bug 1761838] Re: On GCE (Juju 2.3.5) when requesting the private IP address of a unit, I always get the FAN IP address. | #13 |
Oh, I'll test this later then and come back.
Den mån 7 feb. 2022 01:05Ian Booth <email address hidden> skrev:
> Is this still an issue in Juju 2.9.22?
> We don't plan on doing any more 2.8 or earlier releases. If it's an issue
> in 2.9 we can fix it.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> On GCE (Juju 2.3.5) when requesting the private IP address of a unit,
> I always get the FAN IP address.
>
> Status in juju:
> Triaged
>
> Bug description:
> First of all, some context.
> I'm using Juju 2.3.5 on GCE and discovered this behavior while deploying
> the Kibana and ElasticSearch charms of omnivector. Although, I don't think
> the charms matter. Both charms are deployed on separate Google VMs, so no
> containers involved. And to be 100% clear, I haven't tried it with an AWS
> controller.
>
> I noticed from the Kibana UI, it couldn't actually reach the
> ElasticSearch unit. While debugging the process, I noticed Fan was
> deployed on both VMs, although I'm not using any LXD containers. And
> both charms used the Fan IP address as their private IP addresses.
> That's why during the relation conversation the ElasticSearch charm
> passed a wrong IP address to Kibana.
>
> Some commands I tried during my quest.
>
> - on my Juju client:
> ```
> juju run --unit elasticsearch/0 'network-get public --ingress-address
> --format yaml'
> 252.1.240.1
> ```
> - in debug-hooks on my Kibana unit, and in python3 shell:
> ```
> >>> unit_get(
> '252.1.224.1'
> >>> network_
> {'ingress-
> '62:b6:
> 252.0.0.0/8', 'address': '252.1.224.1'}]}]}
> ```
>
> When you need more information, always happy to provide it.
>
> Thanks,
> Gregory
>
> To manage notifications about this bug go to:
> https:/
>
>