[1.30]kubernetes-control-plane stuck in "Waiting to retry addon deployment"

Bug #2067302 reported by Jeffrey Chang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Control Plane Charm
New
Undecided
Unassigned

Bug Description

In SQA test run - https://solutions.qa.canonical.com/testruns/ee98a4cb-be40-4f9f-9d40-0a98fefe609f
, deploying charmed k8s 1.28 on AWS.
kubernetes-control-plane/1 stuck in "Waiting to retry addon deployment" for 1 hr.

Debug log has below for every 2 min or so
2024-05-22 17:48:37 WARNING unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 Failed to get unit file state for kube-apiserver.service: No such file or directory
2024-05-22 17:48:37 WARNING unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 Failed to get unit file state for snap.kube-apiserver.service: No such file or directory
2024-05-22 17:48:37 DEBUG unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 enabled
2024-05-22 17:48:37 INFO unit.kubernetes-control-plane/1.juju-log server.go:325 kube-masters:3: Checking if snap.kube-apiserver.daemon is active (0 / 6)
2024-05-22 17:48:37 DEBUG unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 active
2024-05-22 17:48:37 WARNING unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 Failed to get unit file state for kube-controller-manager.service: No such file or directory
2024-05-22 17:48:37 WARNING unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 Failed to get unit file state for snap.kube-controller-manager.service: No such file or directory
2024-05-22 17:48:37 DEBUG unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 enabled
2024-05-22 17:48:37 INFO unit.kubernetes-control-plane/1.juju-log server.go:325 kube-masters:3: Checking if snap.kube-controller-manager.daemon is active (0 / 6)
2024-05-22 17:48:37 DEBUG unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 active
2024-05-22 17:48:37 WARNING unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 Failed to get unit file state for kube-scheduler.service: No such file or directory
2024-05-22 17:48:37 WARNING unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 Failed to get unit file state for snap.kube-scheduler.service: No such file or directory
2024-05-22 17:48:37 DEBUG unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 enabled
2024-05-22 17:48:37 INFO unit.kubernetes-control-plane/1.juju-log server.go:325 kube-masters:3: Checking if snap.kube-scheduler.daemon is active (0 / 6)
2024-05-22 17:48:37 DEBUG unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 active
2024-05-22 17:48:37 WARNING unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 Failed to get unit file state for kube-proxy.service: No such file or directory
2024-05-22 17:48:37 WARNING unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 Failed to get unit file state for snap.kube-proxy.service: No such file or directory
2024-05-22 17:48:37 DEBUG unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 enabled
2024-05-22 17:48:37 INFO unit.kubernetes-control-plane/1.juju-log server.go:325 kube-masters:3: Checking if snap.kube-proxy.daemon is active (0 / 6)
2024-05-22 17:48:37 DEBUG unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 active
2024-05-22 17:48:37 WARNING unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 Failed to get unit file state for kubelet.service: No such file or directory
2024-05-22 17:48:37 WARNING unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 Failed to get unit file state for snap.kubelet.service: No such file or directory
2024-05-22 17:48:37 DEBUG unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 enabled
2024-05-22 17:48:37 INFO unit.kubernetes-control-plane/1.juju-log server.go:325 kube-masters:3: Checking if snap.kubelet.daemon is active (0 / 6)
2024-05-22 17:48:37 DEBUG unit.kubernetes-control-plane/1.kube-masters-relation-changed logger.go:60 active
2024-05-22 17:48:37 INFO unit.kubernetes-control-plane/1.juju-log server.go:325 kube-masters:3: status-set: waiting: Waiting to retry addon deployment

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.