Managed Kubernetes
Latest
Frequently Asked Questions
Solutions
How Tos
Internal Only
Templates
Powered By

Title
Message
Create new category
What is the title of your new category?
Edit page index title
What is the title of the page index?
Edit category
What is the new title of your category?
Edit link
What is the new title and URL of your link?
Nodes Report Offline After Attaching to New BareOS Cluster
Copy Markdown
Open in ChatGPT
Open in Claude
Problem
- New cluster remain in "pending" state after nodes are attached to it.
- Nodes in this cluster remain offline as pf9-kube fails to start. The following errors are seen in /var/log/pf9/kube/kube.log.
Waiting for "local_apiserver_running" to evaluate to true ...Waiting for "local_apiserver_running" to evaluate to true ...Waiting for "local_apiserver_running" to evaluate to true ...Waiting for "local_apiserver_running" to evaluate to true ...- The following error can be seen in /var/log/pf9/kubelet log.
kubelet[4686]: E0117 976804 4686 kubelet_node_status.go:94] Unable to register node "[node IP address ]" with API server: Post https://127.0.0.1:443/api/v1/nodes: dial tkubelet[4686]: E0117 011489 4686 kubelet.go:2268] node "[node IP address" not foundkubelet[4686]: E0117 111855 4686 kubelet.go:2268] node "<node IP ddress]" not found........kubelet[4686]: E0117 976804 4686 kubelet_node_status.go:94] Unable to register node "[node IP address]" with API server: Post https://127.0.0.1:443/api/v1/nodes: dial tkubelet[4686]: E0117 011489 4686 kubelet.go:2268] node "[node IP address]" not foundkubelet[4686]: E0117 111855 4686 kubelet.go:2268] node "[node IP address]" not foundEnvironment
- Platform9 Managed Kubernetes - All Versions
Cause
Nodes used to create the cluster were a part of another cluster previously and were not cleaned up/deauthorized properly after being detached from the cluster.
Resolution
- Remove/purge all the pf9 packages from the node and verify, as shown below.
xxxxxxxxxx# dpkg --remove --force-remove-reinstreq [pf9-packagename]# dpkg --purge --force-all [pf9-packagename]- Ensure that the following directories have been removed after removal of the packages.
directory '/var/opt/pf9' not empty so not removeddirectory '/var/log/pf9' not empty so not removeddirectory '/opt/pf9' not empty so not removeddirectory '/etc/pf9' not empty so not removed- Reboot the node.
- Install the pf9 agent on the nodes again.
- Authorize the nodes to the Management Plane once the pf9 agent is successfully installed.
- Proceed with cluster creation.
VariableType to search · ESC to discard
GlossaryType to search · ESC to discard
InsertType to search · ESC to discard
No matches
Last updated on
Was this page helpful?
Discard Changes
Do you want to discard your current changes and overwrite with the template?
Archive Synced Block
Message
Create new Template
What is this template's title?
Delete Template
Message