Bug 1806792 - [4.4] Dockercfg secret is not cleaned up when token is deleted
Summary: [4.4] Dockercfg secret is not cleaned up when token is deleted
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: openshift-controller-manager
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.4.0
Assignee: Adam Kaplan
QA Contact: wewang
URL:
Whiteboard: devex
Depends On: 1765294
Blocks: 1779282
TreeView+ depends on / blocked
 
Reported: 2020-02-25 03:45 UTC by wewang
Modified: 2020-05-04 11:39 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: pull secrets for the internal registry sometimes would not be deleted when their associated token was deleted Consequence: stale pull secrets for the internal registry would remain associated with kubernetes service accounts Fix: owner references were established between the internal registry pull secret and its associated token secret Result: pull secrets are always deleted if the associated token is deleted
Clone Of: 1765294
Environment:
Last Closed: 2020-05-04 11:39:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift openshift-controller-manager pull 67 0 None closed [release-4.4] Bug 1806792: Use OwnerRefs to clean up SA pull secrets 2020-10-28 18:48:47 UTC

Comment 4 Adam Kaplan 2020-03-30 15:09:00 UTC 
Reopening. This likely caused the regression in https://bugzilla.redhat.com/show_bug.cgi?id=1785023.
Comment 5 Adam Kaplan 2020-04-01 17:24:45 UTC 
Moving back to VERIFIED - fix for regression is being tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1785023 and its dependent BZs.
Comment 7 errata-xmlrpc 2020-05-04 11:39:48 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-2020:0581
Note You need to log in before you can comment on or make changes to this bug.