Merge pull request #277 from sradco/update_OperatorConditionsUnhealth…

…y_alert_name Update OperatorConditionsUnhealth alert name
kubevirt · Dec 26, 2024 · d534621 · d534621
2 parents 3b6aff3 + 1a38f89
commit d534621
Show file tree

Hide file tree

Showing 2 changed files with 35 additions and 0 deletions.
diff --git a/docs/runbooks/OperatorConditionsUnhealthy.md → ...d_runbooks/OperatorConditionsUnhealthy.md b/docs/runbooks/OperatorConditionsUnhealthy.md → ...d_runbooks/OperatorConditionsUnhealthy.md
diff --git a/docs/runbooks/HCOOperatorConditionsUnhealthy.md b/docs/runbooks/HCOOperatorConditionsUnhealthy.md
@@ -0,0 +1,35 @@
+# HCOOperatorConditionsUnhealthy
+
+## Meaning
+
+This alert triggers when the HCO operator conditions or its secondary resources
+are in an error or warning state.
+
+## Impact
+
+Resources maintained by the operator might not be functioning correctly.
+
+## Diagnosis
+
+Check the operator conditions:
+
+```bash
+kubectl get HyperConverged kubevirt-hyperconverged -n kubevirt -o jsonpath='{.status.conditions}'
+```
+
+## Mitigation
+
+Based on the information obtained during the diagnosis procedure, try to
+identify the root cause within the operator or any of its secondary resources,
+and resolve the issue.
+
+<!--DS: If you cannot resolve the issue, log in to the
+link:https://access.redhat.com[Customer Portal] and open a support case,
+attaching the artifacts gathered during the diagnosis procedure.-->
+
+<!--USstart-->
+If you cannot resolve the issue, see the following resources:
+
+- [OKD Help](https://www.okd.io/help/)
+- [#virtualization Slack channel](https://kubernetes.slack.com/channels/virtualization)
+<!--USend-->