Comment 2 for bug 1850862

This time, I don't think so. We pared down the 10.0.0.0/8 to 10.244.0.0/15. If you check out the bundles, the succeeding run has 10.244.0.0/15 in both the juju-no-proxy setting and passed into the containerd no_proxy. If the large CIDR was causing the failure, that would mean juju-no-proxy doesn't support it, but containerd does support large CIDRs. I assumed that's not the case, is it?