Bug 1887886 - [release 4.5] IO doesn't recognize namespaces - 2 resources with the same name in 2 namespaces -> only 1 gets collected
Summary: [release 4.5] IO doesn't recognize namespaces - 2 resources with the same nam...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Insights Operator
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.5.z
Assignee: Marcell Sevcsik
QA Contact: Pavel Šimovec
URL:
Whiteboard:
Depends On: 1888165
Blocks: 1889318
TreeView+ depends on / blocked
 
Reported: 2020-10-13 14:12 UTC by Marcell Sevcsik
Modified: 2021-01-20 05:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: IO didn't recognize namespaces. Consequence: If a collected resource is present in multiple namespaces(always using the same name) only 1 of the was collected. Fix: During the gathering consider the namespace of the resource. Result: If a collected resource is present in multiple namespaces(always using the same name) all of them will be collected and put into a separate namespace folder.
Clone Of: 1881905
: 1889318 (view as bug list)
Environment:
Last Closed: 2021-01-20 05:49:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift insights-operator pull 219 0 None closed [release 4.5] Bug 1887886: Add the namespace to the gatherers reports to avoid conflicts 2021-01-11 10:57:42 UTC
Red Hat Product Errata RHBA-2021:0033 0 None None None 2021-01-20 05:49:51 UTC

Comment 3 Pavel Šimovec 2021-01-14 13:25:36 UTC 
I have created 2 machinesets with the same name and both were collected, in separate folders
VERIFIED on 4.5.0-0.ci-2021-01-11-225944
Comment 5 errata-xmlrpc 2021-01-20 05:49:27 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.27 bug fix 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/RHBA-2021:0033
Note You need to log in before you can comment on or make changes to this bug.