[release-1.24] 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

[est-suse]

Validated on Version:

f575bd1cc6ac19995e014bb5fde8bd98164dad05

k3s version v1.24.13+k3s-f575bd1c (f575bd1c)
go version go1.19.8

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:

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

May 17 18:12:24 ip-172-31-4-200 k3s[13479]: panic: failed to normalize server token; must be in format K10<CA-HASH>::<USERNAME>:<PASSWORD> or <PASSWORD>
May 17 18:12:36 ip-172-31-4-200 k3s[13497]: time="2023-05-17T18:12:36Z" 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>"
May 17 18:17:19 ip-172-31-4-200 k3s[13886]: time="2023-05-17T18:17:19Z" level=info msg="Managed etcd cluster bootstrap already complete and initialized"
May 17 18:17:24 ip-172-31-4-200 k3s[13886]: time="2023-05-17T18:17:24Z" level=info msg="Reconciling bootstrap data between datastore and disk"