Epic Goal

• provide a better message, description, and fix methodology for customers that see this alert

Why is this important?

• part of an overall 4.9 initiative to improve OOTB alerting in the core Openshift platform

Scenarios

1. An admin of Openshift sees MCDRebootError critical alert, and would like to know the cause and fix

Acceptance Criteria

• See: https://issues.redhat.com/browse/OCPPLAN-6068
• And https://docs.google.com/spreadsheets/d/1pUyKv9as562phraM1Er4jZXZnppayDEhnL02XvjW3c8/edit#gid=2089184919

Dependencies (internal and external)

1. None

Previous Work (Optional):

1. None

Open questions::

1. None

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>