https://rancher.com/ logo
#general
Title
# general
a

adamant-kite-43734

11/16/2022, 4:17 PM
This message was deleted.
r

red-waitress-37932

11/16/2022, 5:25 PM
what's your rancher and vsphere version? I'm on 2.6.9/7U2 and I had no trouble with that step. also, check if the user you are trying to log in as has all the permissions from this page: https://docs.ranchermanager.rancher.io/how-to-guides/new-user-guides/launch-kubernetes-with-[…]nodes-in-an-infra-provider/vsphere/create-credentials
I think I read somewhere that you need at least vsphere 6.7, but 7.x is probably better 🙂
b

broad-yak-96898

11/24/2022, 12:17 AM
Hi, unfortunately it appears you’re hitting this known issue. https://github.com/rancher/rancher/issues/39300 It looks to be tentatively scheduled for release in Rancher v2.7.1
r

red-waitress-37932

11/24/2022, 9:07 AM
they said they're creating cloud credentials, though, not deleting them. so they can't be in use 🙂
c

creamy-autumn-87994

12/06/2022, 1:10 AM
I have the same problem creating a cred with 2.7.0 and vcenter 7.0.3. I double-checked the permissions for the vcenter role. There must be something missing from the documentation because I was able to create the credential using an admin account.
I take that back. Something funky with using a domain user. I created a local vsphere user and it worked fine.
r

red-waitress-37932

12/08/2022, 3:30 PM
interesting. that might be @loud-dog-19653's problem as well
I think I had some other problem with creating a domain user, which is why I used a local user right away. didn't occur to me that this could
b

brash-journalist-8547

01/23/2023, 5:01 PM
same problem here deleting old credentials.
r

red-waitress-37932

01/23/2023, 5:02 PM
that was 2 months ago 😄
which version are you on?
rancher version
if I read this correctly, it's fixed in 2.7.2-rc1
but the thing that's fixed is just a user-unfriendly error message
assuming that the error message you're getting is "Index with name by-cloud-cred does not exist", that error message could be telling you that you cannot delete credentials that are still in use. so check if those credentials are still being used in any cluster 🙂
b

brash-journalist-8547

01/23/2023, 6:36 PM
Ill check it out, pretty sure it is not used. Only realy started affter upgrading from 2.6.7 to 2.6.9
All good, thanks, Ill check it out!
Not in use. Also when I modify a credential it creates a new credential... Very weird, just going to wait til a release fixes whatever it is. For now the one credential I want to use is there and working
r

red-waitress-37932

01/25/2023, 5:29 PM
yeah if there's not a pressing issue, that's fine. I'm guessing you'll eventually upgrade to 2.7.2+ and hopefully get a more helpful from that version
10 Views