Comment 2 for bug 1943786

By "vip" I mean the IP that's assigned to the overall application. I think they did not exist prior to Juju version 2.9.7.

The bug here is the first problem you described; that charms should be able to find daemons listening at other applications' IPs.

I have confirmed that the daemon on each unit is fully functional and can be found at that unit's address. But none of them can be found by way of the application IP.

For clarity about my deployments, I have two development charms that get related to each other. The first charm populates relation data with its IP, and the second charm will use that IP to attempt a connection. In the case of Juju versions lower than 2.9.7, the first charm provides a list of individual unit IPs. On later versions, it will provide the application IP. The second charm attempts the connection. When using the application IP, the second charm looks for a listening daemon at <application-ip>:<port> and finds nothing. When using a list of units' addresses, the second charm looks for listening daemons at <unit-0-ip>:<port>, <unit-1-ip>:<port>, or <unit-2-ip>:<port> and succeeds.