egress-subnets not equivalent to --via
Bug #1880072 reported by
Paul Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned |
Bug Description
The documentation at https:/
Case 1)
juju model-config egress-
juju relate mattermost admin/othermode
Case 2)
juju relate mattermost admin/othermode
However, with Juju 2.8-rc2, in my testing, for case 1, cs:postgresql charm adds entries to pg_hba.conf for the k8s internal subnet, whereas in case 2 it behaves as I expect and adds entries for the specified network.
description: | updated |
Changed in juju: | |
assignee: | nobody → Ian Booth (wallyworld) |
status: | Triaged → In Progress |
tags: | added: bundles |
Changed in juju: | |
milestone: | 2.8.1 → 2.8-next |
Changed in juju: | |
milestone: | 2.8-next → none |
To post a comment you must log in.
It looks like there's 2 code paths here.
When a unit enters scope, the relation data is set up and initial ingress and egress info is added to the relation data. It seems there's a bug in this code which does not fall back to the model default egress-subnets if --via is not used.
Then there's the network-get hook command which prints out the network info and which does seem to do the right thing.
So if the charm gets its network info straight from relation data and not network-get, then that could explain the observed behaviour.