| 2021-09-16 03:51:47 |
Connor Chamberlain |
bug |
|
|
added bug |
| 2021-09-21 21:42:15 |
John A Meinel |
juju: importance |
Undecided |
High |
|
| 2021-09-21 21:42:15 |
John A Meinel |
juju: status |
New |
Incomplete |
|
| 2021-09-30 20:06:53 |
Connor Chamberlain |
juju: status |
Incomplete |
New |
|
| 2021-09-30 20:06:55 |
James Troup |
juju: status |
New |
Confirmed |
|
| 2021-09-30 20:08:15 |
Connor Chamberlain |
description |
Juju 2.9.7 fixed LP1922133 [0], which allowed Sidecar charms to populate their vips, rather than a list of unit addresses, in relation data. Charms looking for a related charm with a vip cannot find a listening daemon at <vip>:<port>. However, a listening daemon can be found at <unit-ip>:<port> for each of the application's units.
The upgrade to Juju >= 2.9.7 breaks relations to charms that are now able to provide vips.
For clarity, some sidecar charms provide a list of unit ips prior to Juju 2.9.7 and switch to providing a single vip at higher versions. The charm receiving the vip should be able to connect by the vip without issue, but it cannot. Development on charms with this functionality must be done on Juju versions lower than 2.9.6.
[0] https://bugs.launchpad.net/juju/+bug/1922133 |
Juju 2.9.7 fixed LP1922133 [0], which allowed Sidecar charms to populate their vips, rather than a list of unit addresses, in relation data. Charms looking for a related charm with a vip cannot find a listening daemon at <vip>:<port>. However, a listening daemon can be found at <unit-ip>:<port> for each of the application's units.
The upgrade to Juju >= 2.9.7 breaks relations to charms that are now able to provide vips.
For clarity, some sidecar charms provide a list of unit ips prior to Juju 2.9.7 and switch to providing a single vip at higher versions. The charm receiving the vip should be able to connect by the vip without issue, but it cannot. Development on charms with this functionality must be done on Juju versions lower than 2.9.6.
[0] https://bugs.launchpad.net/juju/+bug/1922133 |
|
| 2021-10-13 16:36:15 |
Connor Chamberlain |
summary |
Connections fail when using a vip with a port in Charmed Operator Framework |
Charms in the Operator Framework get a default Kubernetes service port of 65535 |
|
| 2021-10-13 16:54:04 |
Connor Chamberlain |
description |
Juju 2.9.7 fixed LP1922133 [0], which allowed Sidecar charms to populate their vips, rather than a list of unit addresses, in relation data. Charms looking for a related charm with a vip cannot find a listening daemon at <vip>:<port>. However, a listening daemon can be found at <unit-ip>:<port> for each of the application's units.
The upgrade to Juju >= 2.9.7 breaks relations to charms that are now able to provide vips.
For clarity, some sidecar charms provide a list of unit ips prior to Juju 2.9.7 and switch to providing a single vip at higher versions. The charm receiving the vip should be able to connect by the vip without issue, but it cannot. Development on charms with this functionality must be done on Juju versions lower than 2.9.6.
[0] https://bugs.launchpad.net/juju/+bug/1922133 |
Juju 2.9.7 fixed LP1922133 [0], which gave juju applications access to their cluster ip, rather than a set of individual unit addresses. When charms relate using cluster ip, no daemons can be found listening at <cluster-ip>:<port>, despite the daemons being fully functional.
This doesn't occur when relations provide unit addresses, as daemons can be found at <unit-ip>:<port>, as expected.
When looking at the kubernetes service descriptions, it appears that charms in the Operator Framework are assigned a port of 65535, which cannot be changed from within the charm.
[0] https://bugs.launchpad.net/juju/+bug/1922133
Edit: rewrote to encapsulate new information on this bug |
|
