Also receiving this error in the nova-api.log file:

"10.129.1.2 POST /services/Cloud/ None:None 400 [Boto/2.0 (linux2)] application/x-www-form-urlencoded text/plain"

Hey guys,

So I wanted to follow up on my own issue and give others out there a solution to my problem.

I was able to get some more information regarding the differences between nova-manage users and keystone users from some community members in the chat room. I think user management should be documented further when distinguishing between Keystone users and Nova users.

Regarding the EC2 credentials and euca-tools, turns out the problem goes back to my "openrc" file. (go figure; after hours and hours of diagnostics). The EC2_ACCESS_KEY environment variable initially set as follows:

EC2_ACCESS_KEY="$KEYSTONE_USERNAME:$KEYSTONE_TENANT"

After listing the stored EC2 tokens via keystone-manage token list, I noticed that one of the tokens was NOT assigned to a keystone tenant. Turns out that when I initially created EC2 credentials for the user, I failed to include a tenant. By removing the $KEYSTONE_TENANT variable from the EC2_ACCESS_KEY I was able to get it to work. For future reference, ensure that your access key matches the keystone username AND/OR tenant exactly how it was entered in the EC2 credential command.