Quantcast
Viewing all articles
Browse latest Browse all 9859

Unable to create tenant as Infrastructure admin on vRA 6.2

Newbie vRA user here, just testing it out for possible deployment into production.

 

As a bit of a "backgrounder":

-I've installed the IaaS component using a domain admin account and vRA identity source is pointed to an SSO on an embedded PSC

-Default tenant is vsphere.local

-I can create a tenant using the administrator@vsphere.local but not the domain account I use to install vRA, or the account I added as infrastructure admin for vsphere.local tenant

 

My questions are:

-Are the aforementioned the correct/expected behavior? It doesn't make sense to me that I'm not able to designate an infra admin that can create tenants other than the default SSO admin account (identity store is pointed to my domain and the domain admin is added to the SSO local administrators group)

-When I try to create reservations (type  : virtual - vSphere) the other tenants I created are not showing under the 'Tenant' dropdown, only thing showing is the vsphere.local (am I missing something here?)

-Under 'Compute Resource' dropdown I'm not able to see resource pools, only the cluster resource. Is this also normal? No option to designate resource pool as compute resource?

 

Thanks a lot in advance.


Viewing all articles
Browse latest Browse all 9859

Trending Articles