metallb app status is in active even when the workload pods are not yet running
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MetalLB Operator |
New
|
Undecided
|
Unassigned | ||
Bug Description
Deployed microk8s charm and the add-ons coredns and metallb.
The juju status for metallb shows active very early even though the pods are still in ContainerCreating state.
Juju Status:
$ juju status -m microk8s-addons
Model Controller Cloud/Region Version SLA Timestamp
microk8s-addons localhost-localhost myk8scloud/
App Version Status Scale Charm Channel Rev Address Exposed Message
coredns active 1 coredns 1.28/stable 101 10.152.183.181 no
metallb active 1 metallb 1.28/stable 4 10.152.183.180 no
Unit Workload Agent Address Ports Message
coredns/0* active idle 10.1.159.72
metallb/0* active idle 10.1.159.69
Offer Application Charm Rev Connected Endpoint Interface Role
coredns coredns coredns 101 0/0 dns-provider kube-dns provider
Microk8s pods status:
$ juju ssh microk8s/leader sudo microk8s.kubectl get po -A -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-system calico-node-b8qzs 1/1 Running 0 13m 10.121.193.91 juju-bd5f0d-2 <none> <none>
kube-system coredns-
kube-system hostpath-
kube-system calico-
microk8s-addons modeloperator-
metallb-system speaker-tdpkp 0/1 ContainerCreating 0 3m 10.121.193.91 juju-bd5f0d-2 <none> <none>
microk8s-addons coredns-0 2/2 Running 0 2m51s 10.1.159.72 juju-bd5f0d-2 <none> <none>
metallb-system controller-
microk8s-addons metallb-0 1/1 Running 0 3m45s 10.1.159.69 juju-bd5f0d-2 <none> <none>
Metallb charm should update its status to active only when all the workload pods are in Running state.
Debug logs for metallb:
https:/
Environment:
juju+lxd cloud
juju 2.9/stable
microk8s 1.28/stable (same for coredns, metallb)
| description: | updated |
| description: | updated |
