Bug 2062070

Summary:	Drop and update API specs that could block upgrades
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Vineet <vbadrina>
Component:	odf-dr	Assignee:	Vineet <vbadrina>
odf-dr sub component:	multicluster-orchestrator	QA Contact:	Jim <cerginba>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	urgent
Priority:	urgent	CC:	kramdoss, madam, mmuench, muagarwa, ocs-bugs, odf-bz-bot, rperiyas
Version:	4.10
Target Milestone:	---
Target Release:	ODF 4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.10.0-194	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-21 09:12:52 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 Vineet 2022-03-09 05:50:01 UTC

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

Currently MirrorPeer spec supports only a single scheduling interval which may cause broken upgrade for customers from 4.10 to 4.11 in near future.

Version of all relevant components (if applicable):
ODF-MCO


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

Can this issue reproducible?
yes

Can this issue reproduce from the UI?
no


Steps to Reproduce:
1. Check MirrorPeer spec


Actual results:
Only single scheduling interval can be given

Expected results:
More than one scheduling interval needs to be supported to maintain stability of the component in future releases.

Comment 3 Vineet 2022-03-09 06:19:46 UTC

Specs 
  To be updated : schedulingInterval
  To be removed : Mode, ReplicationSecretName

Comment 7 Jim 2022-04-05 08:30:36 UTC

The bug has been verified after seeing that multiple options for scheduling intervals are possible:
https://drive.google.com/file/d/1GzyBWY9F5tF1Va1U8agUJC7c1rPM39Ki/view?usp=sharing