nova doesn't work unless using -no-cache option

Asked by JonC

Hi All,

I have a question that i know someone can answer because it's a straightforward one.

Symptom:
When running Nova commands, it is trying to reach an incorrect management server and therefore fails everytime. (I verify this by doing the --debug command). However, when I use the --no-cache option, which means it won't use the authentication cache, everything works normal.

Actions Taken with no success:
-Removed all openstack related packages by doing --purge remove and then re-installed everything
-deleted the entire sql database

Despite all of this, it is still trying to reach a server I had set up previously which is incorrect. Where is it getting this "cached" information from and how do I remove it? Thank you!

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Solved by:
JonC
Solved:
Last query:
Last reply:
Revision history for this message
JonC (jc-openstack) said :
#1

I found out that my keyring was being cached in my ~/.local folder and I had to delete python_keyring.