Node is not given a hostname on first boot after install

[agracey]

You need an extra reboot for the hostname to get set. This causes issues with the k3s node name getting changed.

I'm not sure this is the right place to file this ticket.

[kkaempf]

Where and when are you trying to set the hostname ?

[kkaempf]

We now usually put

spec:
  cloudConfig:
    hostname: ros-node-{{ trunc 4 .MachineID }}

into the machine registration to have the hostname set during initial deployment.

Maybe this should be made standard in all examples ? (It certainly needs more documentation 😉)

[agracey]

I hadn't set anything so was just taking the default rancher-xxxxx that got added. I'll add the specific line to see if it changes the behavior in my set up.

[agracey]

Confirmed this is not an issue when the hostname is set in the cloudConfig settings

[mudler]

FYI it is documented here: https://rancher-sandbox.github.io/cOS-toolkit/docs/reference/cloud_init/#stagesstage_idstep_namehostname