Ask Your Question

What's causing permission error with Vmware Vcenter/ESX 4.1.0 on Grizzly?

asked 2013-04-09 09:58:50 -0500

anonymous user


updated 2013-04-10 13:27:57 -0500

smaffulli gravatar image


I installed and configured the new Grizzly release and now I want to make some test with VMware vCenter 4.1.0, but when I try to boot a virtual machine, there is a stack trace about permission into Nova-compute log file:

2013-04-09 16:05:12.529 4589 CRITICAL nova.virt.vmwareapi.driver [-] In vmwareapi:callmethod, got this exception: Error(s) NoPermission occurred in the call to RetrieveProperties

Is this a known issue?


edit retag flag offensive close merge delete


Have you looked at the permissions on vCenter?

hartsock gravatar imagehartsock ( 2013-04-30 20:37:09 -0500 )edit

Do you still need help with this?

hartsock gravatar imagehartsock ( 2013-05-02 23:46:32 -0500 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2013-04-29 11:51:56 -0500

hartsock gravatar image

Well, "NoPermission" on vCenter typically means the user you used to login doesn't have the permissions needed to do something. The fact that this happened on RetrieveProperties probably means that the driver tried to look at something it doesn't have permissions to look at. Check user roles.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2013-04-09 09:58:50 -0500

Seen: 353 times

Last updated: Apr 10 '13