Login
Log in using an SSO provider:
Fedora Account System
Red Hat Associate
Red Hat Customer
Login using a Red Hat Bugzilla account
Forgot Password
Create an Account
Red Hat Bugzilla – Bug 2134052
Home
New
Search
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh112 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
Migrated Products
[?]
This site requires JavaScript to be enabled to function correctly, please enable it.
Bug 2134052
-
[RDR] Relocate operation never completes when Failover and Relocate operations are done one after another via UI
Summary:
[RDR] Relocate operation never completes when Failover and Relocate operation...
Keywords
:
Status
:
CLOSED DUPLICATE of
bug 2219460
Alias:
None
Product:
Red Hat OpenShift Data Foundation
Classification:
Red Hat Storage
Component:
odf-dr
Sub Component:
---
ramen
multicluster-orchestrator
volume-replication-operator
unclassified
Version:
4.12
Hardware:
Unspecified
OS:
Unspecified
Priority:
unspecified
Severity:
urgent
Target Milestone:
---
Target Release
:
---
Assignee:
Shyamsundar
QA Contact:
Aman Agrawal
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+
depends on
/
blocked
Reported:
2022-10-12 09:08 UTC by
Aman Agrawal
Modified:
2023-08-09 17:00 UTC (
History
)
CC List:
6 users
(
show
)
gshanmug
muagarwa
ocs-bugs
odf-bz-bot
sagrawal
srangana
Fixed In Version:
Doc Type:
If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
2023-08-02 07:28:02 UTC
Embargoed:
Attachments
(Terms of Use)
Links
System
ID
Private
Priority
Status
Summary
Last Updated
Github
RamenDR ramen issues 283
0
None
open
Check and ensure managed cluster condition availability, before processing relocation
2023-02-13 22:16:55 UTC
Github
RamenDR ramen issues 714
0
None
open
Allow relocation only if current sync time is within the replication schedule
2023-02-13 22:16:55 UTC
Comment 20
Aman Agrawal
2023-08-02 07:28:02 UTC
*** This bug has been marked as a duplicate of
bug 2219460
***
Note
You need to
log in
before you can comment on or make changes to this bug.