-
Bug
-
Resolution: Done
-
Major
-
1.2.0.Final
-
False
-
False
-
Undefined
-
---
-
---
-
-
2021 Week 10-12 (from Mar 8)
KogitoRuntime status is currently showing a history of the latest status. The way conditions are expected to behave is like a collection of the latest status of each different type.
{
"lastTransitionTime": "2021-02-18T12:37:11Z",
"status": "True",
"type": "Deployed"
}
{
"lastTransitionTime": "2021-02-18T12:37:11Z",
"message": "servicemonitors.monitoring.coreos.com \"kafka-decision\" already exists",
"reason": "ReconciliationFailure",
"status": "False",
"type": "Failed"
}
{
"lastTransitionTime": "2021-02-18T12:37:12Z",
"status": "True",
"type": "Deployed"
}
{
"lastTransitionTime": "2021-02-18T12:37:12Z",
"message": "servicemonitors.monitoring.coreos.com \"kafka-decision\" already exists",
"reason": "ReconciliationFailure",
"status": "False",
"type": "Failed"
}
{
"lastTransitionTime": "2021-02-18T12:37:13Z",
"status": "True",
"type": "Deployed"
}
- is related to
-
KOGITO-3105 Missing status for failures for KogitoRuntime CRs
-
- Closed
-
-
KOGITO-4731 Conditions should reflect latest evaluated status - Review comments
-
- Resolved
-