Well, that was a convoluted bug, but I've worked out what's going on. Basically, the bug is in nova-cloud-controller and not nova-compute, specifically in the bit where it sets the api_version on the relation between nova-cloud-controller and nova-compute.
In nova-cloud-controller in hooks/nova_cc_hooks.py in `def auth_token_config()` the the api_version is read from the /etc/nova/api-paste.ini file, which is called from `def _auth_config()` called from `def keystone_compute_settings()` which is called ultimately and set on the relation in `def cloud_compute_relation_changed()`.
All would be good, but sadly the 'api_version' key doesn't appear in the relevant section of the /etc/nova/api-paste.ini file which is in `templates/mitaka/api-paste.ini`.
The fix is probably going to be to just add `api_version` to the ./api-paste.ini template, but it needs to be checked that this is a valid field, etc.
I'll change the bug to nova-cloud-controller, and remove it from nova-compute.
Hi Przemyslaw
Well, that was a convoluted bug, but I've worked out what's going on. Basically, the bug is in nova-cloud- controller and not nova-compute, specifically in the bit where it sets the api_version on the relation between nova-cloud- controller and nova-compute.
In nova-cloud- controller in hooks/nova_ cc_hooks. py in `def auth_token_ config( )` the the api_version is read from the /etc/nova/ api-paste. ini file, which is called from `def _auth_config()` called from `def keystone_ compute_ settings( )` which is called ultimately and set on the relation in `def cloud_compute_ relation_ changed( )`.
All would be good, but sadly the 'api_version' key doesn't appear in the relevant section of the /etc/nova/ api-paste. ini file which is in `templates/ mitaka/ api-paste. ini`.
The fix is probably going to be to just add `api_version` to the ./api-paste.ini template, but it needs to be checked that this is a valid field, etc.
I'll change the bug to nova-cloud- controller, and remove it from nova-compute.