Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

So I think I found the root cause: In my nova.conf I have the following options set: quantum_admin_tenant_name= service quantum_admin_username= quantum quantum_admin_password= <quantum password=""> when an instance is talking to the metadata service it uses a token with these credentials, and based of that token, it gets the tenant-id. In my case the tenant-id in the token is service, and the service tenant is not able to see the active ports for tenant member which created the instance. If I change around the credentials in nova.conf to something like: quantum_admin_tenant_name= member quantum_admin_username= user1 quantum_admin_password= <user1 password=""> then I'm able to get the metadata for the instance. what's the recommended solution for this issue? has anyone else seen this in folsom with quantum?