-
Task
-
Resolution: Done
-
Critical
-
None
-
None
-
3
-
False
-
None
-
False
-
Yes
-
-
-
RHOAM Sprint 43
WHY
We need to ensure that we are not missing any components when migrating from OO to OBO.
WHAT
A number of PrometheusRules were mistakenly removed when implementing the OO uninstall logic. The aim of this ticket is to bring back those removed PrometheusRules. Most of these rules were from integreatly-operator/pkg/products/observability/prometheusRules.go. Rather than reusing the integreatly-operator/pkg/products/observability/ folder, it's probably best to put these PrometheusRules in a new file called integreatly-operator/pkg/products/monitoringcommon/prometheusRules.go.
HOW
The missing tests can be determined by installing RHOAM from the OBO feature branch and then running the e2e test "C04 - Verify Alerts exist". Here is the C04_output.txt from a recent run as a starting point.
TESTS
- C04 - Verify Alerts exist - Link
DONE
- The removed PrometheusRules are once again created on fresh RHOAM installs
- The "C04 - Verify Alerts exist" e2e test is passing again
- is related to
-
MGDAPI-5884 Fix e2e tests failing on OBO feature branch
- Closed
- mentioned on