NTP charm is not subnet-aware & picks non-accessible peer addresses
Bug #1777022 reported by
Paul Gear
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| NTP Charm |
New
|
Undecided
|
Unassigned | ||
Bug Description
If the units on which the NTP subordinate charm is installed are multi-homed, the charm does not always pick the right interface for each peer, and sometimes ends up picking unreachable unit addresses: https:/
The charm should either test and use only accessible addresses, or use all unit addresses.
Revision history for this message
| Stuart Bishop (stub) wrote | #1 |
To post a comment you must log in.
Juju 2.3 provides specific bind and ingress addresses to solve this sort of issue.
Some sort of fallback will of course be needed if we need to support older deployments.
Machines added with the manual provider may be a wildcard here, since their networking is not under Juju control. 'juju relate ... via ...' might help here (https:/