Bug 1881061

Summary: openshift-user-workload-monitoring namespace missing from must-gather
Product: OpenShift Container Platform Reporter: Simon Pasquier <spasquie>
Component: MonitoringAssignee: Simon Pasquier <spasquie>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: low Docs Contact:
Priority: medium    
Version: 4.5CC: alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 16:43:33 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:

Description Simon Pasquier 2020-09-21 13:25:08 UTC
Description of problem:
The must-gather archive doesn't contain data about the openshift-user-workload-monitoring namespace.

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

How reproducible:
Always

Steps to Reproduce:
1. Collect a must-gather from a running cluster.
2.
3.

Actual results:
Nothing about pods, configmaps, statefulsets for the openshift-user-workload-monitoring namespace.


Expected results:
Information about pods, configmaps, statefulsets for the openshift-user-workload-monitoring namespace.


Additional info:
N/A

Comment 3 Junqi Zhao 2020-09-24 09:37:16 UTC
tested with 4.6.0-0.nightly-2020-09-24-015627,no matter user workload is enabled or not, must-gather can collect info for openshift-user-workload-monitoring, example:
enabled user workload
$ ls -al gather_umw/must-gather.local.6830418692825711993/quay-io-openshift-release-dev-ocp-v4-0-art-dev-sha256-d89f7f5e38a6d97434ca10c003314f9fd28d91d9e522f8e9431a41bce3279d4d/namespaces/openshift-user-workload-monitoring/
total 56
drwxr-xr-x. 13 juzhao juzhao 4096 Sep 24 16:34 .
drwxr-xr-x. 54 juzhao juzhao 4096 Sep 24 16:34 ..
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:34 apps
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:34 apps.openshift.io
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:34 autoscaling
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:34 batch
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:34 build.openshift.io
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:34 core
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:34 discovery.k8s.io
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:34 image.openshift.io
drwxr-xr-x.  6 juzhao juzhao 4096 Sep 24 16:34 monitoring.coreos.com
-rwxr-xr-x.  1 juzhao juzhao 1780 Sep 24 16:43 openshift-user-workload-monitoring.yaml
drwxr-xr-x.  7 juzhao juzhao 4096 Sep 24 16:34 pods
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:34 route.openshift.io

disabled user workload
$ ls -al gather_no_uwm/must-gather.local.7301714593380513233/quay-io-openshift-release-dev-ocp-v4-0-art-dev-sha256-d89f7f5e38a6d97434ca10c003314f9fd28d91d9e522f8e9431a41bce3279d4d/namespaces/openshift-user-workload-monitoring/
total 48
drwxr-xr-x. 11 juzhao juzhao 4096 Sep 24 16:50 .
drwxr-xr-x. 54 juzhao juzhao 4096 Sep 24 16:50 ..
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:50 apps
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:50 apps.openshift.io
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:50 autoscaling
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:50 batch
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:50 build.openshift.io
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:50 core
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:50 discovery.k8s.io
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:50 image.openshift.io
-rwxr-xr-x.  1 juzhao juzhao 1780 Sep 24 16:59 openshift-user-workload-monitoring.yaml
drwxr-xr-x.  2 juzhao juzhao 4096 Sep 24 16:50 route.openshift.io

Comment 6 errata-xmlrpc 2020-10-27 16:43:33 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.6 GA Images), 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:4196