Bug 2114501

Summary: [RDR] User is able to set value 0 minutes as Sync schedule while creating DR Policy and it reports 'Sync' as Replication policy and gets Validated on a RDR setup
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Aman Agrawal <amagrawa>
Component: management-consoleAssignee: Sanjal Katiyar <skatiyar>
Status: CLOSED CURRENTRELEASE QA Contact: Aman Agrawal <amagrawa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.11CC: ckumar, edonnell, gshanmug, jefbrown, kramdoss, muagarwa, nthomas, ocs-bugs, odf-bz-bot, olakra, sheggodu, skatiyar
Target Milestone: ---   
Target Release: ODF 4.12.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.12.0-79 Doc Type: Bug Fix
Doc Text:
.`async` replication can no longer be set to `0` Previously, you could enter any value for `Sync schedule`. This meant you could set `async` replication to `0`, which caused an error. With this update, a number input has been introduced that does not allow a value lower than 1. `async` replication now works correctly.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-08 14:06:28 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:
Bug Depends On:    
Bug Blocks: 2094357, 2107226    
Attachments:
Description Flags
UX Mockup none

Comment 3 Mudit Agarwal 2022-08-03 05:37:34 UTC 
I am not convinced this as a blocker for a tech preview feature.
We can educate a tech preview user to be more cautious while passing these arguments.

Karthick, can we reduce the severity and move it out to 4.12?
Comment 4 gowtham 2022-08-03 05:52:58 UTC 
This is a very minor issue, While displaying the DRPolicy list page it will show as a Sync, but in All DR and MirrorPeer CR, it won't mark as sync. It is not a blocker, just a display issue.
Comment 5 Mudit Agarwal 2022-08-03 08:40:04 UTC 
Thanks Gowtham, moving this out of 4.11
Comment 8 Mudit Agarwal 2022-08-03 10:25:13 UTC 
If this is not a TP blokcer, it will not be fixed in a z-stream
Comment 10 Mudit Agarwal 2022-08-03 13:47:45 UTC 
If it is just a display issue I don't think it is any kind of blocker. Please justify the blocker? flag, it can be marked as a known issue but definitely not a blocker
Comment 12 Mudit Agarwal 2022-08-04 07:16:06 UTC 
Adding it as a known issue, Gowtham please fill the doc text.
Comment 13 Chandan 2022-10-11 07:17:49 UTC 
Created attachment 1917218 [details]
UX Mockup

UX recommendation for the following bug/issue.
Comment 30 Red Hat Bugzilla 2023-12-08 04:29:50 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days