[vSphere][beats relation] Graylog Charm will respond on the wrong NIC

[Peter Jose De Sousa]

Hello,

Problem:

When hosting graylog on a multi-homed VM (two subnets) and relating filebeat over CMR the relation will configure filebeat in subnet B with NIC A, but when filebeat in B attempts to connect the VM will respond on subnet B, not A. As expected.

Detail:

Spaces are not currently supported on vSphere [1] so this bug is just to document the limitation, that when hosting graylog on a VM with two nics it is not possible to configure bindings so that the charm responds on the correct NIC.

Workaround:

Use filebeats logstash_hosts configuration key to set the subnet B NIC as a logstash host or force communication through the NIC with IP route policies.

[1] https://juju.is/docs/spaces

[Eric Chen (eric-chen)]

This issue was pending over year. We will close it. Furthermore, we will manage the issue in github in the future. Please raise the issue in github if needed
https://github.com/canonical/layer-filebeat/issues