Bug 1958245 - cluster-etcd-operator: static pod revision is not visible from etcd logs
Summary: cluster-etcd-operator: static pod revision is not visible from etcd logs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.8
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.8.0
Assignee: Sam Batschelet
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-07 13:56 UTC by Sam Batschelet
Modified: 2021-07-27 23:07 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-27 23:07:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-etcd-operator pull 586 0 None open Bug 1958245: etcd/pod: print static pod revision in logs 2021-05-07 13:59:06 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 23:07:42 UTC

Description Sam Batschelet 2021-05-07 13:56:49 UTC 
Description of problem: when debugging in CI or via must-gather it is nice to have an understanding of the current static pod revision.


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


How reproducible: 100 %


Steps to Reproduce:
1.
2.
3.

Actual results: etcd logs do not reverence the static pod revision


Expected results: reference to static pod rev in the container and logs make triage of revision churn quicker.


Additional info:
Comment 5 errata-xmlrpc 2021-07-27 23:07:25 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.