Endpoints of peer relation aren't guaranteed to be in the same network space
Bug #1861381 reported by
Aurelien Lourot
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When deploying several units of the same charm, if the endpoints of a peer relation aren't bound to a network space and if there are several spaces to be chosen from and if there is no default space, the endpoints might indeed end up in different spaces. For some charms like charm-hacluster, where the units would like to reach and communicate with each other, this is problematic, see https:/
One could argue that the user has to bind these endpoints to a network space, but we think that many users would expect peer units to be able to reach each other without taking any extra step. What do you think?
(Juju version: 2.7.1)
Revision history for this message
| Richard Harding (rharding) wrote | #1 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| importance: | Wishlist → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
We try to have Juju not "guess" and rather folks are explicit in their setups. We can try to find some patterns as the spaces work continues but for now the best thing we can offer is declaring the endpoint binding for what space you want it on.