Nodes Report Offline After Attaching to New BareOS Cluster

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.
Copy
  • The following error can be seen in /var/log/pf9/kubelet log.
Copy

Environment

  • 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

  1. Remove/purge all the pf9 packages from the node and verify, as shown below.
Copy
  1. Ensure that the following directories have been removed after removal of the packages.
Copy
  1. Reboot the node.
  2. Install the pf9 agent on the nodes again.
  3. Authorize the nodes to the Management Plane once the pf9 agent is successfully installed.
  4. Proceed with cluster creation.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Next to read:
Issues Retrieving Pod/Container Log Information via Kubectl on Hosts Having Proxy Configured

© 2025 Platform9. All Rights Reserved

On This Page
Nodes Report Offline After Attaching to New BareOS ClusterProblemEnvironmentCauseResolution