Bug 2218190
| Summary: | [release-4.14] Alert 'ClusterObjectStoreState' is not triggered when RGW interface is unavailable | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Divyansh Kamboj <dkamboj> |
| Component: | ceph-monitoring | Assignee: | Divyansh Kamboj <dkamboj> |
| Status: | CLOSED ERRATA | QA Contact: | akarsha <akrai> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.14 | CC: | akrai, amohan, dkamboj, hnallurv, jolmomar, kramdoss, muagarwa, nthomas, odf-bz-bot, uchapaga |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | ODF 4.14.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 4.14.0-130 | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 2214524 | Environment: | |
| Last Closed: | 2023-11-08 18:52:10 UTC | Type: | --- |
| 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: | 2214524 | ||
| Bug Blocks: | |||
|
Description
Divyansh Kamboj
2023-06-28 11:55:40 UTC
Hey Akarsha, You'll need to change the test case for this. ODF/Rook used to run a routine that regularly created a bucket and then wrote/read the bucket to test the RGW health, now the status checking is removed. We now need to reflect the "Readyness" of the deployment and the "Connected" nature of status of the CephObjectStore. You can forcefully set the rgw pods to not be "Ready" thus triggering the alert. You can try and do that by changing the ReadinessProbe to something that always returns failure. Moving it to QA as needs changes in test. @akrai you can forcefully make the rgw pods not ready using these steps
Step 1: Get the current YAML configuration of the deployment
kubectl get deployment rook-ceph-rgw-ocs-storagecluster-cephobjectstore-a -n <namespace> -o yaml > deployment.yaml
Step 2: Edit the deployment.yaml file to update the readiness probe
You can use any text editor to modify the file. For example, using nano:
nano deployment.yaml
Inside the deployment.yaml file, locate the readinessProbe section and update it as follows:
readinessProbe:
exec:
command:
- /bin/bash
- -c
- |
#!/usr/bin/env bash
exit 100
initialDelaySeconds: 30
periodSeconds: 10
Save the changes and exit the text editor.
Step 3: Apply the updated YAML configuration to the deployment
kubectl apply -f deployment.yaml -n <namespace>
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat OpenShift Data Foundation 4.14.0 security, enhancement & bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:6832 |