https://rancher.com/ logo
Title
s

sticky-electrician-32652

01/19/2023, 2:24 AM
Hello, was anyone successful in creating downstream RKE clusters using the VSphere Cloud Driver on a vSphere 8 environment? The rancher support matrix doesn’t seem to indicate vSphere 8 support(https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-7-0/). I’m having a particular issue where newly provisioned nodes from node pools never get powered on after being cloned from a template/VM. It seems like pod response indicates an HTTP 500 response. I couldn’t find a related GH issue. Would like to know if anyone else was successful with a vSphere 8 deployment.
a

agreeable-oil-87482

01/19/2023, 6:47 AM
I've been able to deploy using a vsphere 8 environment
s

sticky-electrician-32652

01/23/2023, 9:11 PM
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

agreeable-oil-87482

01/23/2023, 10:35 PM
Yes and yes
s

sticky-electrician-32652

01/24/2023, 12:26 AM
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

agreeable-oil-87482

01/24/2023, 7:55 AM
I'm using admin but we have documented the role permissions required. Are you using those and where are you adding the user?
s

sticky-electrician-32652

01/24/2023, 6:06 PM
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

agreeable-oil-87482

01/24/2023, 6:10 PM
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

sticky-electrician-32652

01/24/2023, 6:23 PM
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

agreeable-oil-87482

01/24/2023, 6:25 PM
Propagate selected?
s

sticky-electrician-32652

01/24/2023, 6:26 PM
Propagate to children, yes.
a

agreeable-oil-87482

01/24/2023, 6:28 PM
Interesting. Can you raise this at https://github.com/rancher/rancher/issues please? I'll look into this.
s

sticky-electrician-32652

01/24/2023, 6:29 PM
👍 will do. Thanks for looking into this!
a

agreeable-oil-87482

01/24/2023, 6:29 PM
Thank you for answering all the questions 😁
s

sticky-electrician-32652

01/24/2023, 7:10 PM
Issue created: https://github.com/rancher/rancher/issues/40291 Thanks again David! Appreciate the help!
a

agreeable-oil-87482

01/24/2023, 7:11 PM
Awesome, thank you
s

sticky-electrician-32652

01/25/2023, 11:12 PM
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

agreeable-oil-87482

01/25/2023, 11:18 PM
Will be interesting to read your observations