Error: "Missing security token (NODETOKEN)" During RKE2 Cluster Deployment of NetOps flow

Products

• Network Observability

Issue/Introduction

During the NetOps flow RKE2 Kubernetes cluster deployment, the automated installation halts while attempting to configure secondary control plane nodes․ The system reports a fatal error regarding a missing security token (NODETOKEN), preventing nodes from joining the cluster․​​​​‌​‍

ERROR MESSAGE: "Missing security token (NODETOKEN)"

SYMPTOMS:

• Deployment automation fails

• Secondary control planes fail to join

• Worker nodes fail to join

CONTEXT: Occurs during automated Ansible cluster initialization․

IMPACT: Prevents complete cluster deployment․

Environment

• NetOps Flow 25.4.x
• Kubernetes: RKE2
• Deployment Tool: Ansible

Cause

The automation queried the wrong server for the token because the first server listed in the inventory list was [IP-address] instead of the primary initialization node [IP-address]․ This mismatch returned an empty variable, causing the failure․

Resolution

1․ IDENTIFY PRIMARY NODE

Find the designated primary initialization node IP address․

EXPECTED: Correct primary node identified․

2․ UPDATE INVENTORY FILE

Path: cd netops-k8s-installer/rke/ansible

Move the primary initialization node to the very top of the [k8s_hosts] list․

EXPECTED: The group indexing matches architectural intent․ NOTE: The automation dynamically pulls the token and cluster join URL from the first server listed․

VERIFY SUCCESS:

• Deployment script identifies the correct primary node

• Script retrieves the generated security token

• Remaining nodes authenticate and join the RKE2 cluster