I've removed ubuntu-fan.
I'm working on a fix for this.
What needs to happen is for the container NIC to use the MTU of the
VXLAN accompanying the Fan bridge (which appears to be correctly offset
from the underlay) rather than the bridge itself.
** No longer affects: ubuntu-fan (Ubuntu)
--
You
** Changed in: juju
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1944080
Title:
[fan-network] Race-condition between "apt update" and dhcp re
I've added the ubuntu-fan package, as fanctl should accommodate the
underlay MTU.
There is a work-around for the Juju case, which I will look to
implement.
** Also affects: ubuntu-fan (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a me
** Changed in: juju
Status: Triaged => In Progress
** Changed in: juju
Milestone: None => 2.9.17
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1936842
Title:
agent cann
Hmm. Now I see that on Canonistack, this is all set up correctly by
default.
2: ens2: mtu 1458 qdisc fq_codel state UP
group default qlen 1000
link/ether fa:16:3e:5f:24:be brd ff:ff:ff:ff:ff:ff
inet 10.48.130.242/17 brd 10.48.255.255 scope global dynamic ens2
valid_lft 85790sec pr
5 matches
Mail list logo
