-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
BU Product Work
-
1
-
False
-
None
-
False
-
OCPSTRAT-835 - Improve upgrades - Reduce False Positives status from operators
-
OTA 223, OTA 224, OTA 225, OTA 226, OTA 227, OTA 228, OTA 229, OTA 230, OTA 231, OTA 233, OTA 243
We need to communicate available and degraded condition definition along with examples to the teams. The intent is to make sure teams are using these status conditions and not avoiding going to degraded = true or available = false just to pass the tests.
Update API godocs and/or create additional documentation with better definitions of degraded and available conditions' setting (true or false).
Working group Slack channel : #wg-operator-degraded-condition
Google doc: https://docs.google.com/document/d/17KXg4xTcOVDzKYz-GYwxy6072N6VTLjD2ReWq8UB0Dk/edit
Definition of done:
- Send an email to aos-devel to the incoming test change in
OTA-362. Also point folks to existing godocs around availability = false and degraded = true - Remind folks that we still wants operators to go availability = false and degraded = true but when it logical situations.