Bug 1965367 - Typo in in etcd-metric-serving-ca resource name
Summary: Typo in in etcd-metric-serving-ca resource name
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.8.0
Assignee: Brad Ison
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-27 14:51 UTC by Brad Ison
Modified: 2021-07-27 23:10 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-27 23:10:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 1185 0 None open Bug 1965367: pkg/operator: Fix typo in etcd-metric-serving-ca resource name 2021-05-27 14:52:05 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 23:10:40 UTC

Description Brad Ison 2021-05-27 14:51:13 UTC
Description of problem:

The name of the resource watched for updates to the etcd metrics CA certificate has a typo. It is currently "etcd-metrics-serving-ca" but should be "etcd-metric-serving-ca" without the extra "s".

Comment 2 Junqi Zhao 2021-05-31 01:54:07 UTC
tested with 4.8.0-0.nightly-2021-05-29-114625, configmap name now is etcd-metric-serving-ca
# oc -n openshift-config get cm etcd-metric-serving-ca
NAME                     DATA   AGE
etcd-metric-serving-ca   1      158m

Comment 5 errata-xmlrpc 2021-07-27 23:10:12 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.8.2 bug fix and security 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-2021:2438


Note You need to log in before you can comment on or make changes to this bug.