[release-1.26] Bootstrap of HA cluster fails with when agent bootstrap token used as server token

[brandond]

• Backport Bootstrap of HA cluster fails with when agent bootstrap token used as server token #7313

[fmoral2]

Validated on Version:

- k3s version v1.26.4+k3s-e8d9ed79 (e8d9ed79

Environment Details

Infrastructure
Cloud EC2 instance

Node(s) CPU architecture, OS, and Version:
Ubuntu

Cluster Configuration:
1 node

Config.yaml:

write-kubeconfig-mode: 0644
debug: true
protect-kernel-defaults: true
selinux: true
token: xxxx.yyyyy
cluster-init: true

Steps to validate the fix

1. Install k3s in commit version
2. Generate a k3s token in format: xxxxxxx.yyyyyy
3. Start server with the token in config.yaml
4. Check logs for error message

Validation Results:

~$ k3s -v
k3s version v1.26.4+k3s-e8d9ed79 (e8d9ed79




~$ k3s token generate

xxxxx.yyyyy


sudo mkdir -p /etc/rancher/k3s
sudo bash -c 'cat <<EOF>/etc/rancher/k3s/config.yaml
write-kubeconfig-mode: 0644
debug: true
protect-kernel-defaults: true
selinux: true
token: xxxx.yyyyy
cluster-init: true
EOF'



Errors logs from journalctl -u k3s:

May 16 18:13:48 ip-172-31-33-249 k3s[324177]: time="2023-05-16T18:13:48Z" level=info msg="Reconciling bootstrap data between datastore and disk"
May 16 18:13:48 ip-172-31-33-249 k3s[324177]: time="2023-05-16T18:13:48Z" level=fatal msg="Failed to reconcile with temporary etcd: failed to normalize server token; must be in format K10<CA-HASH>::<USERNAME>:<PASSWORD> or <PASSWORD>"