Bug 1013088 - [Doc] Following the keystone identity service steps results in configuration error message during token-get
Summary: [Doc] Following the keystone identity service steps results in configuration ...
Keywords:
Status: CLOSED DUPLICATE of bug 1101784
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-Installation_and_Configuration_Guide
Version: 3.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: RHOS Documentation Team
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-27 19:59 UTC by Jon Jozwiak
Modified: 2015-02-09 23:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-08 22:37:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jon Jozwiak 2013-09-27 19:59:15 UTC
Document URL: https://access.redhat.com/site/documentation/en-US/Red_Hat_OpenStack/3/pdf/Installation_and_Configuration_Guide/Red_Hat_OpenStack-3-Installation_and_Configuration_Guide-en-US.pdf

Section Number and Name: 5.10 Validating the Identity Service Installation

Describe the issue: If you follow the steps in chapter 5 for installing the Openstack Identity Service, the validation in section 5.10 fails on both the keystonerc_user being able to see users in the user-list as well as the keystone token-get failing.  

Suggestions for improvement: The problem is due to SERVICE_TOKEN and SERVICE_ENDPOINT still being set from section 5.6.  Add an additional step either after 5.6 on in 5.10 before doing any validation to unset the variables:
    unset SERVICE_TOKEN
    unset SERVICE_ENDPOINT 

Additional information: Here is the error given when running the keystone token-get:

[root@hostname ~(keystone_admin)]# keystone token-get
WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).
Configuration error: Client configured to run without a service catalog. Run the client using --os-auth-url or OS_AUTH_URL, instead of --os-endpoint or OS_SERVICE_ENDPOINT, for example.

Comment 2 Summer Long 2013-11-26 01:55:49 UTC
Updating priority to match severity.

Comment 4 Andrew Dahms 2015-02-08 22:37:30 UTC
Dear Jon,

Thank you for raising this bug, and my sincere apologies for the time it has taken to receive a response.

This issue is also raised in BZ#1101784, where work on this content is being consolidated.

I am closing this bug as a duplicate, but please let me know if you have any further issues with the documentation.

Kind regards,

Andrew

*** This bug has been marked as a duplicate of bug 1101784 ***


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