Bug 2086544 - ovn-k master daemonset on hypershift shouldn't log token
Summary: ovn-k master daemonset on hypershift shouldn't log token
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.11.0
Assignee: Patryk Diak
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-16 12:00 UTC by Casey Callendrello
Modified: 2022-08-10 11:12 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 11:12:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 1446 0 None open Bug 2086544: Stop passing hosted cluster token as a parameter to ovnkube-master 2022-05-16 12:16:24 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:12:15 UTC

Description Casey Callendrello 2022-05-16 12:00:00 UTC 
Because we pass +x to bash, it means that the ovn-k master token is output and logged. This shouldn't happen.

While we're here, we should also add in a wait loop for the token file to show up, just in case the token-minter is slow to initialize.
Comment 6 errata-xmlrpc 2022-08-10 11:12:07 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069
Note You need to log in before you can comment on or make changes to this bug.