Bug 1316200
Summary: | OSP director 8 not setting up keystone endpoints correctly for the undercloud | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Harry Rybacki <hrybacki> |
Component: | instack-undercloud | Assignee: | James Slagle <jslagle> |
Status: | CLOSED ERRATA | QA Contact: | Arik Chernetsky <achernet> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.0 (Liberty) | CC: | achernet, bnemec, dbecker, dmellado, mburns, morazi, rhel-osp-director-maint, sclewis, slinaber |
Target Milestone: | ga | ||
Target Release: | 8.0 (Liberty) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | instack-undercloud-2.2.6-1.el7ost | Doc Type: | Bug Fix |
Doc Text: |
Cause:
Previously, there was a trailing slash (/) on the keystone endpoint in the service catalog.
Consequence:
Services that queries the service catalog for the keystone endpoint and did not allow for an optional trailing slash on the endpoint would fail in different ways.
For instance, tempest would fail with a 404 in its log since the url was not constructed correctly:
2016-03-09 09:22:52.020 18640 ERROR tempest Details: {u'message': u'The resource could not be found.', u'code': 404, u'title': u'Not Found'}
2016-03-09 09:22:52.020 18640 ERROR tempest
Fix:
The keystone endpoint in the service catalog no longer has a trailing slash on the end, which is the correct way to define an endpoint.
Result:
All services using the keystone endpoint from the service catalog operate as expected.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-04-07 21:49:09 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Harry Rybacki
2016-03-09 16:25:40 UTC
This problem is also present in upstream master. I've linked a patch that should fix this, which will need to be backported. 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. https://rhn.redhat.com/errata/RHEA-2016-0604.html |