Ask Your Question
0

Why is nova ignoring microvesions

asked 2018-06-14 08:35:21 -0500

I have a Pike install that has been upgraded all the way from Kilo and I can't seem to get nova to honor microversions. What is going wrong?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2018-06-14 08:43:10 -0500

Answering my own question here after hammering it out with the nova devs on irc. Older versions used /v2/%(tenant_id)s as the path for the nova endpoint, this locks you into v2 compatibility mode where microversions are ignored. Changing the endpoint path to /v2.1 will enable the v2.1 api with microversions. The queens release of magnum uses a server group with soft anti affinity which requires nova microversion 2.15, this is where I first discovered with the legacy endpoint still present in my deployment. Also note that some nova clients need a trailing slash /v2.1/ to correctly parse http vs https. This should probably get fixed in nova client but using this workaround will get you by until all the clients everywhere are fixed.

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

Stats

Asked: 2018-06-14 08:35:21 -0500

Seen: 12 times

Last updated: Jun 14 '18