ssh-setup/nova doesn't work with keystone v3

Bug #1767433 reported by Iain Lane
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Auto Package Testing
Fix Released
Undecided
Julian Andres Klode

Bug Description

We have a new cloud region "bos01" which apparently requires the use of a new API version which, in part, means that the old "nova" command doesn't work :( -

$ nova list
ERROR: (http://foo/v3/v2.0/tokens): The resource could not be found. (HTTP 404)

The 'openstack' command works with this API version and seems to be the superset of all the previous commands (nova, glance, neutron, ...):

$ openstack server list

Unfortunately if you look at autopkgtest and autopkgtest-cloud we use 'nova' a lot, e.g. in the script to set up new instances:

https://salsa.debian.org/ci-team/autopkgtest/blob/master/ssh-setup/nova

In order to use bos01 we need to be able to speak the v3 APIs or the new CLI tools. For information, it looks like 'openstack' doesn't work with the old (v2?) API.

I assume it'd be best to rewrite our tools to use the APIs instead of invoking the CLI commands and parsing their output. I don't know at all but hopefully it'd be possible/not too hard to convince the to speak v2 and v3 as appropriate.

:/

Revision history for this message
Iain Lane (laney) wrote :

OK, the horrifying part here isn't true - you just need a new enough version of the client tools. It looks like xenial's version is good enough, so the scripts which run on the worker hosts will be okay.

Client *API* scripts need to be updated for keystone v3 though.

Revision history for this message
Julian Andres Klode (juliank) wrote :
Iain Lane (laney)
Changed in auto-package-testing:
status: New → In Progress
assignee: nobody → Julian Andres Klode (juliank)
Revision history for this message
Julian Andres Klode (juliank) wrote :

Fixes have been committed and a test run confirmed they are working.

Changed in auto-package-testing:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.