Bug 2030229 - Mirroring status card reflect wrong data
Summary: Mirroring status card reflect wrong data
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.10.0
Assignee: gowtham
QA Contact: Aman Agrawal
URL:
Whiteboard:
Depends On:
Blocks: 2031692
TreeView+ depends on / blocked
 
Reported: 2021-12-08 09:07 UTC by Pratik Surve
Modified: 2022-03-10 16:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:32:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot mirroring card (27.43 KB, image/png)
2021-12-08 09:07 UTC, Pratik Surve
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 10634 0 None open Bug 2030229: Fix mirroring status card reflect wrong data 2021-12-08 13:13:41 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:33:11 UTC

Description Pratik Surve 2021-12-08 09:07:33 UTC
Created attachment 1845199 [details]
screenshot mirroring card

Description of problem:
Mirroring status card reflect wrong data 

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

How reproducible:


Steps to Reproduce:
1. Deploy DR cluster 
2. Do some failover's 
3. check mirroring status 

Actual results:
Pie chat shows wrong data 

Expected results:


Additional info:

Comment 6 errata-xmlrpc 2022-03-10 16:32:46 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.10.3 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:0056


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