© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Do you have an idea of what needs to be tweaked?
It is consistently only one out of 3 units that runs into this error, so I don't think this is due to a misconfiguration.
This is not a problem we have seen in k8s deployments on jammy, and it is not necessarily reproducible with an OpenStack deployment. My guess is that the network is somehow more overloaded on jammy.