Bug 2053104 - [vSphere CSI driver Operator] hw_version_total metric update wrong value after upgrade nodes hardware version from `vmx-13` to `vmx-15`
Summary: [vSphere CSI driver Operator] hw_version_total metric update wrong value afte...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.10
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: 4.11.0
Assignee: Hemant Kumar
QA Contact: Penghao Wang
URL:
Whiteboard:
Depends On:
Blocks: 2060213
TreeView+ depends on / blocked
 
Reported: 2022-02-10 14:33 UTC by Penghao Wang
Modified: 2022-08-10 10:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2060213 (view as bug list)
Environment:
Last Closed: 2022-08-10 10:49:18 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift vmware-vsphere-csi-driver-operator pull 77 0 None open Bug 2053104: Do not cache node check results between runs 2022-02-28 16:10:07 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:49:37 UTC

Comment 2 Jan Safranek 2022-02-23 15:16:27 UTC 
Good catch! I am going to close this in favor of a similar BZ from a customer.

*** This bug has been marked as a duplicate of bug 2042446 ***
Comment 3 Hemant Kumar 2022-02-28 02:01:34 UTC 
While the metric bug is same as linked one. The upgradeable=False not being cleared is a different error and needs a fix esp. for 4.10.
Comment 9 errata-xmlrpc 2022-08-10 10:49:18 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 (Important: OpenShift Container Platform 4.11.0 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-2022:5069
Note You need to log in before you can comment on or make changes to this bug.