Bug 2108716
| Summary: | Deletion of Application deleting the pods but not PVCs | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Amarnath <amk> | |
| Component: | odf-dr | Assignee: | Shyamsundar <srangana> | |
| odf-dr sub component: | ramen | QA Contact: | kmanohar | |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | ||
| Severity: | high | |||
| Priority: | unspecified | CC: | bmekhiss, edonnell, gshanmug, muagarwa, ocs-bugs, odf-bz-bot, olakra, srangana | |
| Version: | 4.11 | |||
| Target Milestone: | --- | |||
| Target Release: | ODF 4.12.0 | |||
| Hardware: | Unspecified | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
.Deletion of Application now deletes pods and PVCs correctly
Previously, when deleting an application from the RHACM console, DRPC did not get deleted. Not deleting DRPC leads to not deleting the VRG as well as the VR. If the VRG/VR is not deleted, the PVC finalizer list will not be cleaned up, causing the PVC to stay in a `Terminating` state.
With this update, deleting an application from the RHACM console deletes the required dependent DRPC and related resources on the managed clusters, freeing up the PVCs as well for required garbage collection.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 2110026 (view as bug list) | 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: | 2110026 | |||
| Bug Blocks: | 2094357, 2107226 | |||
|
Description
Amarnath
2022-07-19 18:49:44 UTC
@amk require must-gather output for ODF and ACM hub to debug the problem. @gshanmug this I suspect is because the UI does not delete the DRPC created for the application (due to lack of integration for the same). Due to which, VRG holds back the PVC on the cluster as it is not deleted as yet. What is the component to move this BZ to? (should we have UI as another sub-component here?) Hi Shyam, I have collected must-gather logs, But our file server is down. Can you help me with any file server where I can post it? Regards, Amarnath (In reply to Amarnath from comment #5) > Hi Shyam, > > I have collected must-gather logs, But our file server is down. > Can you help me with any file server where I can post it? I really do not have any location handy. Can you let us know if DRPlacementControl resource exists on the hub cluster for the application that was deleted? and if yes, paste its YAML output. Further if it exists, please post the VolumeReplicationGroup resource from the ManagedCluster where the workload was deleted as well. Both resources are to be found in the same namespace as the application. The above would be enough to prove the conjecture that the issue is non-deletion of DRPC by the application UI. Hi @srangsrangana, As mentioned in the screenshots attached. I tried deleting the application from Web console of ACM(multi cloud cluster console). Regards, Amarnath Moving this out to 4.12 after discussing with Karthick, we don't want to risk a regression at this point of time. Please provide the doc text. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |