Bug 2108088
| Summary: | in v2.0.3 - Provider stuck in addon deleting state even after all consumsers are deleted | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | suchita <sgatfane> |
| Component: | odf-managed-service | Assignee: | Kaustav Majumder <kmajumde> |
| Status: | VERIFIED --- | QA Contact: | suchita <sgatfane> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.10 | CC: | aeyal, dbindra, ebondare, fbalak, kmajumde, odf-bz-bot, sgatfane |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 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
suchita
2022-07-18 12:29:34 UTC
The root cause of looks like the leftover of storage consumers in storage consumer list even after offboarding of the consumer. This is already reported to this bug https://bugzilla.redhat.com/show_bug.cgi?id=2069389 Looking at this, deployer is working as expected. I think a bug needs to be raised on the product side to remove storage consumers after offboarding. Ohad WDYT? @sgatfane Can you provide the storage consumer CR yaml after the consumer has offboarded? Seems after offboarding the Storage Consumer CR is marked for deletion but doesnot get deleted immediately. We might have to check our uninstallation logic to include deletionTimestamp. @kmajumde Storage Consumer will not get deleted until all of the rook resources that are owned by it are deleted. The underlying rook resource might not get deleted because of an unclean removal of PV/PVC on the consumer cluster side. Let's try to identify which rook resource is stuck on deleting, but does not get deleted, and try to address that. Try it on the latest build As the issue is not always reproducible, I asked the team members who created clusters lately if anyone faced any issues with uninstallation. I'll gather the responses and update the BZ. Verified on Deployer version v2.0.12 (on QE addon/Dev Addon ) . The issue is not reproducible single time with 5 uninstallations. so Considering it is fixed on the latest version. Marking BZ as verified. |