This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes

Bug 905801

Summary: Include keystone_authtoken in quantum.conf
Product: Red Hat OpenStack Reporter: Mark McLoughlin <markmc>
Component: openstack-quantumAssignee: Bob Kukura <rkukura>
Status: CLOSED ERRATA QA Contact: Ofer Blaut <oblaut>
Severity: medium Docs Contact:
Priority: high    
Version: 2.1CC: apevec, chrisw, dyocum, lpeer, markmc, ndipanov, oblaut, ykaul
Target Milestone: snapshot4Keywords: Triaged
Target Release: 2.1   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: 2012.2.3-4.el6ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 887822 Environment:
Last Closed: 2013-03-21 15:05:04 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 892339    

Description Mark McLoughlin 2013-01-30 02:52:27 EST
+++ This bug was initially created as a clone of Bug #887822 +++

+++ This bug was initially created as a clone of Bug #887334 +++

  6) In our default /etc/quantum/quantum.conf we should also document the 
     [keystone_authtoken] section and put the keystone_authtoken defaults
     in /usr/share/quantum/quantum-dist.conf

 - Don't forget the [keystone_authtoken] ... that should also go in quantum.conf
   and its defaults in quantum-dist.conf

--- Additional comment from Bob Kukura on 2013-01-29 21:44:35 EST ---


I'm not sure about the [keystone_authtoken] config you refer to. I don't see that used in the quantum source, except the l3_agent config above that does not use that config section.



keystone_authtoken options are registered by the authtoken middleware

See also bug #876763 and bug #888725
Comment 2 Bob Kukura 2013-02-22 14:14:16 EST
Fixed in dist-git packaging.
Comment 6 errata-xmlrpc 2013-03-21 15:05:04 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.