-
Task
-
Resolution: Won't Do
-
Normal
-
1.20.0
-
False
-
-
False
-
No
-
RC2
Origin: tests/products/h25-verify-rate-limiting-can-be-disabled-and-reenabled-by-follow.md
Description
Note: double-check that workload webapp is not already deployed before attempting to deploy it by checking if workload-web-app namespace exists in the cluster.
This test case should prove that it is possible for SRE to disable/enable rate limiting service without affecting the RHOAM services availability
Prerequisites
- access to `cloud-services-qe-reporting@redhat.com
` mailing list
- workload webapp should be running on the cluster https://github.com/integr8ly/workload-web-app/
Steps
- Go to https://github.com/RHCloudServices/integreatly-help/blob/master/sops/rhoam/rate-limit/disable.md
- Follow and validate the steps in SOP for disabling rate limit service
- Open the RHOAM Grafana Console in the redhat-rhmi-observability namespace
open "https://$(oc get route grafana-route -n redhat-rhoam-observability -o=jsonpath='{.spec.host}')"
- Select the Workload App dashboard
Validate that requests to 3scale application are not failing after rate limiting service was disabled
Note: Downtime of up to 5 minutes is acceptable as per the service definition - Search for alerts in `cloud-services-qe-reporting@redhat.com
` mailing list
Make sure no critical alert is firing (you might see some alerts with severity "warning")
- Follow and validate the steps in SOP for re-enabling rate limit service
- Go back to Workload App dashboard
Validate that requests to 3scale application are not failing after rate limiting service was enabled again
Note: Downtime of up to 5 minutes is acceptable as per the service definition - Open the RHOAM Grafana Console in the redhat-rhoam-customer-monitoring-operator namespace
open "https://$(oc get route grafana-route -n redhat-rhoam-customer-monitoring-operator -o=jsonpath='{.spec.host}')"
- Validate that the requests made by workload-web-app are displaying in the graphs
- Search for alerts in `cloud-services-qe-reporting@redhat.com
` mailing list
Make sure no critical alert is firing (you might see some alerts with severity "warning")
General guidelines for testing
- is blocked by
-
MGDAPI-3860 C05B - alerts - Verify alerts are exposed and no critical alerts have fired
-
- Closed
-
-
MGDAPI-3861 A17B - installation - Verify the Go functional tests were successful
-
- Closed
-
-
MGDAPI-3862 A36 - installation - RHOAM operator log should not contain errors and irrelevant warnings
-
- Closed
-
-
MGDAPI-3863 H21B - products - Verify all products using the workload-web-app
-
- Closed
-