-
Notifications
You must be signed in to change notification settings - Fork 54
ERROR (BadRequest): Expecting apiKey (HTTP 400) #94
Comments
This actually looks like an issue with python-novaclient 2.27.0. I tried providing all the variables to nova and received the same error. Rolling back to 2.26.0 fixed it for me.
|
Hey @pozgo -- thanks for the bug report. That error output is coming from python-novaclient, as @sjafferali noted above. You might want to double-check your supernova configuration to make sure your credentials are entered correctly. |
To expand on my previous reply, there appears to be an issue with the python-novaclient 2.27.0 update that causing the error "ERROR (BadRequest): Expecting apiKey (HTTP 400)."
Since supernova calls nova with arguments, it is affected as well.
|
HI, Thanks for such a quick reply. After downgrading the nova client to 2.26.0 seems to work again. BTW. Still after having supernova run and getting output there is small error.
|
This issue is also present in 2.28.0. I downgraded to 2.26.0 as suggested here, and I can now access Rackspace. |
+1, same as @DanielSmedegaardBuus I updated to 2.28.0 this morning and suddenly started receiving the 400 bad request errors as well. ERROR (BadRequest): Expecting apiKey (HTTP 400) I made no changes to my .supernova credentials file; downgraded back to 2.26.0 and functionality was restored. |
https://review.openstack.org/#/c/221570/ Once that goes through, or someone comments on it, that should fix the problem The problem is that every nova client call checks for the api_version, but the rackspace api endpoint has that disabled. |
Just a heads up. I pulled down the most recent 2.31.0 (after https://review.openstack.org/#/c/221570/ @gtmanfred mentioned above has been merged) and this issue seems to have been resolve. |
After running
git pull
MacOS 10.10.5
The text was updated successfully, but these errors were encountered: