Bug 2243244

Summary:	[RDR] UI shows misleading VolumeSynchronizationDelay critical alert until lastGroupSyncTime is available in DRPC
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Sidhant Agrawal <sagrawal>
Component:	odf-dr	Assignee:	rakesh-gm <rgowdege>
odf-dr sub component:	ramen	QA Contact:	Sidhant Agrawal <sagrawal>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	muagarwa, rgowdege
Version:	4.14
Target Milestone:	---
Target Release:	ODF 4.16.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.16.0-94	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-07-17 13:09:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sidhant Agrawal 2023-10-11 11:29:46 UTC

Description of problem (please be detailed as possible and provide log
snippests):

During the verification of Bug 2232242, it was observed that the VolumeSynchronizationDelay critical alert is being fired after applying DRPolicy to the application until lastGroupSyncTime is available in DRPC. 

Alert message in UI:
```
Syncing of volumes (DRPC: busybox-subscription-placement-1-drpc, Namespace: busybox-subscription) is taking more than thrice the scheduled snapshot interval. This may cause data loss and a backlog of replication requests.
```

This alert is misleading because it shows a critical alert for three snapshot intervals without waiting for those intervals, giving the false impression that there is a replication issue.


Version of all relevant components (if applicable):
OCP: 4.14.0-0.nightly-2023-09-24-044110
ODF: 4.14.0-137.stable
(ceph version 17.2.6-138.el9cp (b488c8dad42b2ecffcd96f3d76eeeecce48b8590) quincy (stable))
ACM: 2.9.0-158 (2.9.0-DOWNSTREAM-2023-09-23-04-31-38)
Submariner: 0.16.0 (iib:581798)
VolSync: 0.7.4

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
2

Can this issue reproducible?
yes

Can this issue reproduce from the UI?
yes

If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Deploy RDR setup and create app for on C1
2. Apply DRPolicy
3. Watch for VolumeSynchronizationDelay critical alerts


Actual results:
VolumeSynchronizationDelay critical alerts are triggered when the app is first deployed and DRPolicy is applied, but they are cleared once lastGroupSyncTime is available.

Expected results:
Alert should reflect that initial sync has not completed while waiting for lastGroupSyncTime to be populated 

Additional info:

Comment 4 Mudit Agarwal 2024-01-16 12:12:41 UTC

Any update on this BZ, are we fixing it in 4.15?

Comment 5 Mudit Agarwal 2024-01-23 10:51:08 UTC

Not a 4.15 blocker

Comment 14 errata-xmlrpc 2024-07-17 13:09:57 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: Red Hat OpenShift Data Foundation 4.16.0 security, enhancement & bug fix 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-2024:4591