ssh-setup/nova doesn't work with keystone v3
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://
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:/
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.
:/
Related branches
- Ubuntu Release Team: Pending requested
-
Diff: 37 lines (+23/-3)1 file modifiedssh-setup/nova (+23/-3)
- Iain Lane: Needs Fixing
-
Diff: 44 lines (+22/-4)1 file modifiedtools/cleanup-instances (+22/-4)
Changed in auto-package-testing: | |
status: | New → In Progress |
assignee: | nobody → Julian Andres Klode (juliank) |
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.