Bug 1825758

Summary: Gather ConfigMaps from openshift-config namespace (backport to 4.3)
Product: OpenShift Container Platform Reporter: Martin Kunc <mkunc>
Component: Insights OperatorAssignee: Martin Kunc <mkunc>
Status: CLOSED ERRATA QA Contact: Angelina Vasileva <anikifor>
Severity: medium Docs Contact: Radek Vokál <rvokal>
Priority: unspecified    
Version: 4.3.0CC: anikifor, avicenzi, inecas, rvokal
Target Milestone: ---   
Target Release: 4.3.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: Added collection of Configurations from ConfigMaps from openshift-config namespace Reason: We want to see if certificates are used for cluster CA and gather other cluster related settings from openshift-config namespace. Result:
Story Points: ---
Clone Of: 1825757
: 1825770 (view as bug list) Environment:
Last Closed: 2020-06-17 20:27:11 UTC Type: ---
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: 1825757    
Bug Blocks: 1825770    

Description Martin Kunc 2020-04-20 07:24:47 UTC
+++ This bug was initially created as a clone of Bug #1825757 +++

+++ This bug was initially created as a clone of Bug #1825756 +++

Description of problem:
Insights operator wasn't collecting cluster wide ConfigMaps from openshift-config. We should add them.

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

How reproducible:


Steps to Reproduce:
1. Install OpenShift 4.2 with enabled Insights Operator
2. Wait until IO collects and sends the archive
3. Look into the archive

Actual results:
Archive is missing ConfigMaps from openshift-config

Expected results:
Archive has ConfigMaps from openshift-config

Additional info:

Comment 3 Angelina Vasileva 2020-06-05 13:45:05 UTC
Fixed and verified in 4.3.0-0.nightly-2020-06-05-071243

Comment 5 errata-xmlrpc 2020-06-17 20:27:11 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:2436