Bug 1913356 - (release-4.7) Implemented gathering specific logs from openshift apiserver operator
Summary: (release-4.7) Implemented gathering specific logs from openshift apiserver op...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Insights Operator
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.7.0
Assignee: Serhii Zakharov
QA Contact: Pavel Šimovec
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-06 15:05 UTC by Serhii Zakharov
Modified: 2021-02-24 15:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: collects logs from openshift-apiserver-operator with following substrings: - "the server has received too many requests and has asked us" - "because serving request timed out and response had been started" Reason: https://access.redhat.com/solutions/5448851 Result:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:50:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift insights-operator pull 273 0 None closed [release 4.7] Bug 1913356: Implemented gathering specific logs from openshift apiserver operator 2021-02-14 12:14:43 UTC
Red Hat Knowledge Base (Solution) 5448851 0 None None None 2021-01-06 15:06:25 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:51:08 UTC

Description Serhii Zakharov 2021-01-06 15:05:10 UTC
Comment 3 Pavel Šimovec 2021-01-13 11:16:46 UTC 
According to documentation, archive was supposed to contain config/pod/{namespace}/logs/.*\.log files
it contains:

        config/pod/openshift-monitoring/logs/prometheus-k8s-0/config-reloader_current.log
        config/pod/openshift-monitoring/logs/prometheus-k8s-0/kube-rbac-proxy_current.log
        config/pod/openshift-monitoring/logs/prometheus-k8s-0/prom-label-proxy_current.log
        config/pod/openshift-monitoring/logs/prometheus-k8s-0/prometheus-proxy_current.log
        config/pod/openshift-monitoring/logs/prometheus-k8s-0/prometheus_current.log
        config/pod/openshift-monitoring/logs/prometheus-k8s-0/prometheus_previous.log
        config/pod/openshift-monitoring/logs/prometheus-k8s-0/thanos-sidecar_current.log
        config/pod/openshift-monitoring/logs/prometheus-k8s-1/config-reloader_current.log
        config/pod/openshift-monitoring/logs/prometheus-k8s-1/kube-rbac-proxy_current.log
        config/pod/openshift-monitoring/logs/prometheus-k8s-1/prom-label-proxy_current.log
        config/pod/openshift-monitoring/logs/prometheus-k8s-1/prometheus-proxy_current.log
        config/pod/openshift-monitoring/logs/prometheus-k8s-1/prometheus_current.log
        config/pod/openshift-monitoring/logs/prometheus-k8s-1/prometheus_previous.log
        config/pod/openshift-monitoring/logs/prometheus-k8s-1/thanos-sidecar_current.log

Verified on commit with hash bcc800977928b28d43dfc3685a716c160402cec0
Comment 6 errata-xmlrpc 2021-02-24 15:50:41 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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-2020:5633
Note You need to log in before you can comment on or make changes to this bug.