When setting preferred-api-version=3 [keystone_authtoken] of neutron.conf should include "auth_version = 3"

Bug #1702278 reported by Amad Ali
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Charm Helpers
New
Undecided
Unassigned
OpenStack Keystone Charm
Invalid
Undecided
Unassigned
OpenStack Neutron API Charm
Triaged
Low
Unassigned

Bug Description

When the cloud is deployed or upgraded with parameter preferred-api-version=3, the keystone_authtoken section of neutron conf gets updated as follows:

----------------
[keystone_authtoken]
auth_uri = http://<***>:5000
auth_url = http://<***>:35357
auth_type = password
project_domain_name = service_domain
user_domain_name = service_domain
project_name = services
username = neutron
password = <***>
signing_dir = /var/cache/neutron

memcached_servers = inet6:[::1]:11211
--------------

It is also required to set parameter "auth_version = 3" in [keystone_authtoken] section of neutron conf which is also a requirement for Cisco ACI integration i.e. for cisco group-based-policy plugin to send v3 requests to keystone.

tags: added: canonical-bootstack
Revision history for this message
Frode Nordahl (fnordahl) wrote :

The issue I have with this is that Cisco ACI really should deduce which API version to use by other means.

The auth_version option is not needed nor used by default, it is not referenced in the upstream Ubuntu installation guide. If you put up a pristine devstack from upstream master right now, everything will be Keystone v3 by default. And you will also see there that no services use the auth_version configuration option.

I am not going to be religious about it, but I still think it to be a unnecessary configuration option.

Revision history for this message
Amad Ali (amad) wrote :

Have submitted a change for review.

https://review.openstack.org/#/c/483323/

However, I will talk to Cisco if they can make this change at their end.

Revision history for this message
James Page (james-page) wrote :

Marking Keystone task as invalid (its already passing the data - so any updates will be scoped to neutron-api).

Changed in charm-keystone:
status: New → Invalid
Changed in charm-neutron-api:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-neutron-api (master)

Change abandoned by Frode Nordahl (<email address hidden>) on branch: master
Review: https://review.openstack.org/483323
Reason: Marking this review as abandoned due to lack of activity in the past 6 months.

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.