metallb app status is in active even when the workload pods are not yet running

Bug #2037054 reported by Hemanth Nakkina
6
This bug affects 1 person
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/localhost 2.9.44 unsupported 12:09:34+05:30

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-864597b5fd-6tt6l 1/1 Running 0 13m 10.1.159.65 juju-bd5f0d-2 <none> <none>
kube-system hostpath-provisioner-7df77bc496-d68k2 1/1 Running 0 13m 10.1.159.67 juju-bd5f0d-2 <none> <none>
kube-system calico-kube-controllers-77bd7c5b-wrj4z 1/1 Running 0 13m 10.1.159.66 juju-bd5f0d-2 <none> <none>
microk8s-addons modeloperator-75cf4bd96b-wnrvw 1/1 Running 0 3m58s 10.1.159.68 juju-bd5f0d-2 <none> <none>
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-5c68c46976-ltcjj 1/1 Running 0 3m 10.1.159.71 juju-bd5f0d-2 <none> <none>
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://pastebin.ubuntu.com/p/Hh3H7sFnrn/

Environment:
juju+lxd cloud

juju 2.9/stable
microk8s 1.28/stable (same for coredns, metallb)

description: updated
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.