Node NotReady as Nodelet is Unable To Start PF9-Kube Due to Broken Packages
Problem
A Cluster Node is reporting offline as pf9-nodeletd service is in a stopped state.
+ install_docker_engine<br>
+ remove_incompatible_packages<br>
+ apt-get -y purge docker lxc-docker docker-engine<br> E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.<br>" func=main.startKubeService file="/pf9/nodelet/nodeletd.go:210"
time="<date:time>" level=warning msg="Trying to start pf9-kube 2501. Failed task on the last run was: Configure Docker" func=main.writeExtensionData file="/pf9/nodelet/nodeletd.go:261"Environment
Platform9 Managed Kubernetes - v4.1
Nodeletd
Cause
The pf9-kube service was unable to purge the packages as some of the packages were broken.
+ install_docker_engine
+ remove_incompatible_packages
+ apt-get -y purge docker lxc-docker docker-engine
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.Resolution
Manually run the below command on the node to fix the broken packages.
Once this command completes successfully the pf9-nodeletd service will start pf9-kube service and the node will be reported as Ready.
PreviousUnable to Start pf9-kube Service Due to Package Hold
NextPod Stuck in Terminating State Due to Inability to Clean Volume subPath Mount
Last updated
