"IP allocation failed" error on vsphere with canal CNI
Bug #2065723 reported by
Jake Nabasny
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MetalLB Operator |
New
|
Undecided
|
Unassigned | ||
Bug Description
When deploying the metallb charm to a new Charmed K8s cluster, the controller pod fails to come up because of an "IP allocation failed" error. The iprange is configured to match the exact IPs of the k8s hosts. This seems to only happen on vsphere when using the Canal CNI. On vsphere with Calico CNI, the same configuration and deployment steps work fine. On a MAAS cloud using Canal CNI, it also works fine. So the issue seems to be the specific combination of vsphere cloud and Canal CNI that the metallb charm is having trouble with.
During deployment, the speaker pods show running and the controller and metallb-0 pods are stuck in pending. Juju status remains in "installing agent" for the metallb unit.
To post a comment you must log in.
