Comment 5 for bug 2002465

Further down the rabbit hole, it seems that the container image doesnt matter - ubuntu or rocky, same effect.
Forcing {% set sst_method = 'rsync' %} in galera.conf.j2 also doesn't help anything.
Manual netcat connection checks on all involved ports succeed.
Dropping MTU on the IP interface to 1500 does not help, neither does setting the MTU in docker's daemon.json
Iperf runs between the nodes show full bandwidth, no error counters on NICs or switch ports (bonds).
tcpdump observation of the SST port shows _no traffic at all_ during the boostrap:
```
# tcpdump -vvv -n -i br-bond0-222 port 4444 or port 4568
tcpdump: listening on br-bond0-222, link-type EN10MB (Ethernet), snapshot length 262144 bytes

```

MaaS did deploy the node with multiple routing tables in the netplan, but they all match up and connectivity tests pass with flying colors.

Something about 22.04, or how kolla-ansible configures it, seems to prevent seeding of mariadb slaves breaking the stack. Having trouble coming up with a rational explanation for why no data is seen between the donor and joiner.