Loading...

XML

Word

Printable

Severity:
Low
Regression:
None
Story Points:
2
Release Blocker:
Rejected
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Target Version:

4.19.0
Target Backport Versions:

4.13.z, 4.12.z, 4.14.z, 4.15.z, 4.17.z, 4.16.z, 4.18.z

Description of problem:

The current "description" annotation of the CoreDNSErrorsHigh alert doesn't provide much context about what's happening and what to do next.

Version-Release number of selected component (if applicable):

4.14.39

How reproducible:

always

Steps to Reproduce:

Deploy OCP and use unhealthy nameservers as upstream for CoreDNS ! Or control DNS pods placement without complying with the standard architecture...

Actual results:

CoreDNSErrorsHigh but the description annotation doesn't provide lots of information about what to do next.

Expected results:

Detailed instructions.

Additional info:

https://access.redhat.com/solutions/5917331

blocks

OCPBUGS-52501 [release-4.13] Add runbook_url for CoreDNSErrorsHigh

impacts account

RFE-5643 [RFE][DNS METRICS] Split CoreDNSErrorsHigh alert rule

relates to

OCPBUGS-52498 [release-4.16] Add runbook_url for CoreDNSErrorsHigh

OCPBUGS-52499 [release-4.15] Add runbook_url for CoreDNSErrorsHigh

OCPBUGS-52500 [release-4.14] Add runbook_url for CoreDNSErrorsHigh

OCPBUGS-52501 [release-4.13] Add runbook_url for CoreDNSErrorsHigh

OCPBUGS-52502 [release-4.12] Add runbook_url for CoreDNSErrorsHigh

OCPBUGS-52497 [release-4.17] Add runbook_url for CoreDNSErrorsHigh

OCPBUGS-52514 [release-4.18] Add runbook_url for CoreDNSErrorsHigh

links to

(4 relates to, 2 links to)