-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
Adjust operator condition severity to honor hierarchy and achieve consistency
-
False
-
-
False
-
Not Selected
-
Proposed
-
Proposed
-
Done
-
Proposed
-
Proposed
-
0% To Do, 4% In Progress, 96% Done
-
-
-
-
OSPK8S Sprint 7, OSPK8S Sprint 8
-
2
-
Moderate
Goal:
- Our operators currently use "False" (i.e. "Not Ready") condition severity in an unpredictable and ad hoc manner, often blurring the lines between info/warning/error, and vary between each other in terms of which are used for similar conditions
- We should make sure all our operators properly report the severity of the various "False" conditions they might encounter, and that they do so consistently across all of them
Acceptance Criteria:
- "False" conditions should be assigned a severity (error, warning or info) depending upon how detrimental they are to forward progress of the reconciliation loop
- Common conditions seen in multiple operators should use the same severity across all of them