Bug 1835090

Summary:	Collect Anonymized CSR
Product:	OpenShift Container Platform	Reporter:	Martin Kunc <mkunc>
Component:	Insights Operator	Assignee:	Alexandre Vicenzi <avicenzi>
Status:	CLOSED ERRATA	QA Contact:	Angelina Vasileva <anikifor>
Severity:	medium	Docs Contact:	Radek Vokál <rvokal>
Priority:	unspecified
Version:	4.5	CC:	avicenzi, inecas, rluders, scuppett
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Feature: Added collection anonymized unapproved Certificate Service Requests. Reason: We want to see if Certificates which are denied, expired or not valid yet at least in their anonymized form. Theys could be a good clue to solve customer issues. Result:	Story Points:	---
Clone Of:
Clones:	1835093 (view as bug list)		Environment:
Last Closed:	2020-07-13 17:38:07 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:
Bug Depends On:
Bug Blocks:	1835093, 1835094

Description Martin Kunc 2020-05-13 05:38:29 UTC

Description of problem:
The task should add collection of Certificate features, which could be used to verify their validity in further stages.


Version-Release number of selected component (if applicable):
4.5

How reproducible:
Look into Insights operator archive for CSR. They are missing.

Steps to Reproduce:
1. Install OCP with some unapproved Certificate signing requests. 
2. Let Insighst Operator collect archive and 
3. look inside to check 

Actual results:
No CSR data

Expected results:
Anonymized CSR exists

Additional info:

Comment 3 Angelina Vasileva 2020-06-11 10:48:35 UTC

Fixed and verified in 4.5.0-0.nightly-2020-06-11-035450.

This link contains verification steps https://kubernetes.io/docs/tasks/tls/managing-tls-in-a-cluster/#create-a-certificate-signing-request-object-to-send-to-the-kubernetes-api

Comment 4 errata-xmlrpc 2020-07-13 17:38: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, 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