Bug 1813288
| Summary: | No alert or status change when all PVCs of MCG Resource are deleted | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Container Storage | Reporter: | Filip Balák <fbalak> |
| Component: | Multi-Cloud Object Gateway | Assignee: | Romy Ayalon <rayalon> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Filip Balák <fbalak> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.3 | CC: | ebenahar, etamir, madam, nbecker, ocs-bugs |
| Target Milestone: | --- | ||
| Target Release: | OCS 4.5.0 | ||
| 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: | 2020-09-16 12:22:23 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: | |||
not in the plan for 4.4. maybe reconsider for 4.5? Somehow this BZ flew under the radar, Filip which PVC is that ? The Mongo PVC which is being used by the core? Add a metric to prometheus (if we don't have it already) and add an alert on that metric. There have been a lot of updates to the statuses and alerts in both 4.4 and 4.5, does it still happen? Yes, I was able to reproduce it with ocs version 4.5.0-448.ci thanks!! |
Description of problem (please be detailed as possible and provide log snippests): There is no alert and state of MCG Resource is not changed if all PVCs for the resource are deleted (It remains Healthy). Version of all relevant components (if applicable): OCP: 4.3.0-0.nightly-2020-03-12-085147 OCS: 4.3-30.07d83470.ocs_4.3 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? no Is there any workaround available to the best of your knowledge? no Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 3 Can this issue reproducible? yes Can this issue reproduce from the UI? yes, but deleting of PVC is more simple from cmd If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. In MCG console go to Resources 2. Create MCG resources like Kubernetes Pools and Backing Stores 3. Delete all PVCs of the resources: $ oc delete pvc -n openshift-storage <resource-pvc> 4. Remove finalizers of the PVCs: $ oc patch pvc -n openshift-storage <resource-pvc> -p '{"metadata":{"finalizers": []}}' --type=merge where <resource-pvc> PVC of created resource. 5. Check in MCG console that there is an alert and that created resources are in Warning or Error state. Actual results: There is no alert and resources don't change status. Expected results: There should be an alert and resources shouldn't be Healthy if their PVCs disappear. Additional info: