Bug 986146 - CONFIG_KEYSTONE_TOKEN_FORMAT value is UUID in Grizzly and PKI in upstream.
CONFIG_KEYSTONE_TOKEN_FORMAT value is UUID in Grizzly and PKI in upstream.
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: openstack-packstack (Show other bugs)
19
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Derek Higgins
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-19 01:07 EDT by Gowrishankar Rajaiyan
Modified: 2013-07-22 02:04 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-07-22 02:04:59 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Gowrishankar Rajaiyan 2013-07-19 01:07:20 EDT
Description of problem: Not sure if this is a bug, but filing it to have this cleared. While generating answer file using packstack, I see difference in CONFIG_KEYSTONE_TOKEN_FORMAT value. In Grizzly I see the value by default is UUID, however in upstream it is PKI.


Version-Release number of selected component (if applicable):
Grizzly: packstack: openstack-packstack-2013.1.1-0.23.dev642.el6ost.noarch
Upstream: packstack: last commit 0ca7d5ac37858e1d5e16c6988fd12296d4f0aba7

How reproducible: Always


Steps to Reproduce:
1. packstack --gen-answer-file=ANSWER_FILE
2. grep CONFIG_KEYSTONE_TOKEN_FORMAT ANSWER_FILE


Actual results:
In Grizzly:
# grep CONFIG_KEYSTONE_TOKEN_FORMAT ANSWER_FILE 
CONFIG_KEYSTONE_TOKEN_FORMAT=UUID

In Upstream:
# grep CONFIG_KEYSTONE_TOKEN_FORMAT ANSWER_FILE
CONFIG_KEYSTONE_TOKEN_FORMAT=PKI


Additional info:
Comment 1 Martin Magr 2013-07-22 02:04:59 EDT
First of of all el6ost is not a Fedora package. In Fedora package PKI is default.

Note You need to log in before you can comment on or make changes to this bug.