Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1488784

Summary: [backport][Ocata] Fix the s3tokens endpoint
Product: Red Hat OpenStack Reporter: Robin Cernin <rcernin>
Component: puppet-barbicanAssignee: Christian Schwede (cschwede) <cschwede>
Status: CLOSED ERRATA QA Contact: Aharon Canan <acanan>
Severity: high Docs Contact:
Priority: high    
Version: 11.0 (Ocata)CC: astupnik, augol, dcadzow, hrybacki, nkinder, srevivo, tachoi
Target Milestone: z5Keywords: FeatureBackport, Triaged, ZStream
Target Release: 11.0 (Ocata)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-barbican-10.4.0-1.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-18 17:17:01 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 Robin Cernin 2017-09-06 08:07:58 UTC 
Description of problem:

This was broken when issue_v2_token was removed, and no one noticed because there are no tests. The good news is, Swift3 is content to move toward supporting the v3 format, so just start inheriting from the v3 controller.

Upstream backport proposed https://review.openstack.org/#/c/501148/
Comment 1 Alex Stupnikov 2018-02-05 09:44:43 UTC 
Upstream backport was merged at Jan-25, please proceed with the bug.
Comment 4 Christian Schwede (cschwede) 2018-04-10 11:18:49 UTC 
*** Bug 1484200 has been marked as a duplicate of this bug. ***
Comment 7 Harry Rybacki 2018-04-18 14:39:50 UTC 
Upstream review[1] merged awhile back -- moving bug to POST.

[1] - https://review.openstack.org/#/c/501148/
Comment 16 errata-xmlrpc 2018-05-18 17:17:01 UTC 
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://access.redhat.com/errata/RHBA-2018:1623