Bug 1806150 - [IPI][OSP] 403 error when deleting a cluster with Swift but without swiftoperator role
Summary: [IPI][OSP] 403 error when deleting a cluster with Swift but without swiftoper...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.5.0
Assignee: Mike Fedosin
QA Contact: David Sanz
URL:
Whiteboard:
Depends On:
Blocks: 1809227
TreeView+ depends on / blocked
 
Reported: 2020-02-22 13:13 UTC by Mike Fedosin
Modified: 2020-08-04 18:01 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1809227 (view as bug list)
Environment:
Last Closed: 2020-08-04 18:01:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 3164 0 None closed Bug 1806150: Skip container deletion if the user doesn't have the required role 2020-06-23 08:44:23 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-08-04 18:01:46 UTC

Description Mike Fedosin 2020-02-22 13:13:12 UTC
When I delete a cloud, which has Swift enabled, without swiftoperator role I get next error from the Swift endpoint:

ERROR Request forbidden: [GET https://swift.example.com/v1/AUTH_7808db451cfc43eaa9acda7d67da8cf1/], error message: <html><h1>Forbidden</h1><p>Access was denied to this resource.</p></html>

Comment 4 David Sanz 2020-03-04 11:39:58 UTC
Verified on 4.5.0-0.nightly-2020-03-04-100655

Comment 6 errata-xmlrpc 2020-08-04 18:01:43 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 (OpenShift Container Platform 4.5 image release 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-2020:2409


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