Bug 2159791 - [RDR] DR workloads remain stuck when deleted [NEEDINFO]
Summary: [RDR] DR workloads remain stuck when deleted
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: csi-driver
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Madhu Rajanna
QA Contact: krishnaram Karthick
URL:
Whiteboard:
: 2225672 (view as bug list)
Depends On:
Blocks: 2107226
TreeView+ depends on / blocked
 
Reported: 2023-01-10 18:11 UTC by Aman Agrawal
Modified: 2024-01-19 15:52 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
.Disaster recovery workloads remain stuck when deleted When deleting a workload from a cluster, the corresponding pods may not terminate with events such as `FailedKillPod`. This may cause delay or failure in garbage collecting dependent DR resources such as the `PVC`, `VolumeReplication`, and `VolumeReplicationGroup`. It would also prevent a future deployment of the same workload to the cluster as the stale resources are not yet garbage collected. Workaround: Reboot the worker node on which the pod is currently running and stuck in a terminating state. This results in successful pod termination and subsequently related DR API resources are also garbage collected.
Clone Of:
: 2209298 (view as bug list)
Environment:
Last Closed:
Embargoed:
rtalur: needinfo? (amagrawa)
rar: needinfo? (rtalur)


Attachments (Terms of Use)

Comment 33 Karolin Seeger 2023-05-02 11:44:25 UTC
Moving the BZ to 4.14.0 as this is not a release blocker.
Waiting for repro/logs.

Comment 48 yati padia 2023-05-22 03:57:10 UTC
Hey Ilya,

Yeah sure that should be fine, but before that, we need to verify if that is affecting the time of must-gather.
We are already facing lots of issues in must-gather. Please feel free to open a bug/REF in must-gather.
I will take care of it.

Thanks,
Yati

Comment 65 Raghavendra Talur 2023-08-29 14:02:19 UTC
*** Bug 2225672 has been marked as a duplicate of this bug. ***


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