-
Epic
-
Resolution: Done
-
Major
-
None
-
Regular Config Check
-
False
-
False
-
Done
-
0% To Do, 0% In Progress, 100% Done
-
Undefined
-
0
-
0
Epic Goal
- As it works today, the MCO checks to see if the current configuration that it expects is as expected only before applying a new configuration.
- The MCO should check configuration regularly so admins know about potential problems sooner.
- The MCO should communicate any discrepancies between expected and on-disk state back to the admin (oc output, console, alert?)
Why is this important?
- It's better to alert admins as soon as possible to configuration differing from what is expected by the MCO. Otherwise they may find out under pressure to complete scheduled maintenance, for example.
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
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>
