We ran into this again today (it's been awhile).
Here's the run: https://solutions.qa.canonical.com/testruns/testRun/8e8c272a-d3f9-4945-8db3-ab265fc1633e
In the run comments you can see our calico config with the CIDR.
We also have this run from yesterday that succeeded using the exact same hardware and config (including our calico CIDR): https://solutions.qa.canonical.com/testruns/testRun/37f1d6c7-9c13-4cc5-84a9-553f32e6af1e
---
This suggests that either our CIDR config is fine or that our CIDR config is incorrect and causing *spurious* errors rather than consistent errors. Any insight?
We ran into this again today (it's been awhile).
Here's the run: /solutions. qa.canonical. com/testruns/ testRun/ 8e8c272a- d3f9-4945- 8db3-ab265fc163 3e
https:/
In the run comments you can see our calico config with the CIDR.
We also have this run from yesterday that succeeded using the exact same hardware and config (including our calico CIDR): /solutions. qa.canonical. com/testruns/ testRun/ 37f1d6c7- 9c13-4cc5- 84a9-553f32e6af 1e
https:/
---
This suggests that either our CIDR config is fine or that our CIDR config is incorrect and causing *spurious* errors rather than consistent errors. Any insight?