https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# vsphere
a
This message was deleted.
a
I've been able to deploy using a vsphere 8 environment
s
thanks for responding! are you using the vsphere node driver to provision your nodes? wondering if you can check your datastore to see if user-data.iso is found in any of the nodes.
a
Yes and yes
s
are you using an vsphere admin user for your deployment? it seems like my issue is related to permissions. curious if you can share what permissions you set for your deployment user
a
I'm using admin but we have documented the role permissions required. Are you using those and where are you adding the user?
s
Yes. I’ve been using the permissions defined here: https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/launch-kubernetes-with[…]nodes-in-an-infra-provider/vsphere/create-credentials FWIW this used to work in vSphere 7. Our admins recently upgraded to vSphere 8. Now it seems to be stuck/failing whenever the cluster provisioner attempts to update 
user-data.iso
to a datastore. A full admin account works, the rancher provided documents do not.
a
Same account, no changes to the role or where the vsphere user was applied, and provisioning stopped working after upgrading to vsphere 8 from 7?
Is your user applied at the global level?
s
Yes, same account with no changes to the role. The user is defined at the global level. I can also confirm the child resources reference the global definition.
a
Propagate selected?
s
Propagate to children, yes.
a
Interesting. Can you raise this at https://github.com/rancher/rancher/issues please? I'll look into this.
s
👍 will do. Thanks for looking into this!
a
Thank you for answering all the questions 😁
s
Issue created: https://github.com/rancher/rancher/issues/40291 Thanks again David! Appreciate the help!
a
Awesome, thank you
s
FWIW, I may have found the necessary updated permissions. Going to dial back the perms and update the ticket with the final solution.
thanks for the help though. i’m glad it wasn’t a vSphere 8 incompatibility 😓
a
Will be interesting to read your observations
21 Views
Open in Slack
PreviousNext
Powered by