https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# vsphere
a
This message was deleted.
a
No issues here. How are you building your template or are you using a cloud image
m
also curious, are you defining your user information in the cloud config yaml section when creating the cluster?
p
We're building our template with Packer - we do some configuration with as a part of the packer build. We're not defining the user info in the cloud config.
a
What are the ssh errors? Also, are you using this for a rke1 or rke2 cluster?
p
I'm seeing the issue with both rke1 and rke2. I'm digging up the specific error and will post it shortly.
a
In your packer builds do you reset 
cloud-init
?
p
No, I don't think so - would that just be stopping cloud-init and removing /var/lib/cloud/?
a
This is what I do
p
I'll give it a try!
a
To add some context - rancher generates an SSH key and mounts it to newly created VMs in vsphere via a cloud init iso. If cloud init isn't cleared it won't ingest any new config and therefore won't accept the ssh key
p
Why would that impact 22.04, but not 20.04?
a
Depends if you used the subiquity installer, or if cloud init was cleared in your older image
p
It wasn't cleared in the older image, but we didn't use subiquity with 20.04.
a
With the subiquity installer which is now default I think it uses cloud init as part of the install process. The older process did not
Which is why you explicitly have to clear it in newer versions
p
that makes sense - thanks for the explanation
a
No worries 👍
p
And as it turned out, that fixed it for me. Thanks again @agreeable-oil-87482!
a
You're welcome 👍
h
Hey David, just wanted to drop a note here and say this thread also fixed my issue with provisioning 22.04 nodes as well. Thanks a bunch!
a
Glad to hear it, you're welcome 👍
76 Views
Open in Slack
PreviousNext
Powered by