You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently only report ERROR state for sync failures and we don't return the actual error message. See this example (UUIDs redacted):
curl -s https://api.poc.parvaeres.io/v1/deployment/... | jq '.Items[0].Errors'
[
"Failed sync attempt to 68db: one or more synchronization tasks are not valid (retried 5 times)."
]
We could even better than the high level error condition by reporting the syncResult and resources in SyncFailed state.
status:
conditions:
- lastTransitionTime: "2020-11-24T21:32:29Z"
message: 'Failed sync attempt to 68db: one
or more synchronization tasks are not valid (retried 5 times).'
type: SyncError
[...]
phase: Failed
retryCount: 5
startedAt: "2020-11-24T21:27:19Z"
syncResult:
resources:
- group: apps.openshift.io
kind: DeploymentConfig
message: the server could not find the requested resource
name: mysql-p07
namespace: ...
status: SyncFailed
syncPhase: Sync
version: v1
The text was updated successfully, but these errors were encountered:
Now the UI displays the actual error messages. But I noticed that sometimes, even when in error state, no specific error messages are contained in the API response.
We currently only report
ERROR
state for sync failures and we don't return the actual error message. See this example (UUIDs redacted):We could even better than the high level error condition by reporting the
syncResult
and resources inSyncFailed
state.The text was updated successfully, but these errors were encountered: