Azure / Azure/orkestra

Workflow node timeout/failure errors not reflected in ApplicationGroup status

Open
#289 2 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
112
Forks
21
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
Failures and timeouts that occur during a workflow node execution are not reflected by the ApplicationGroup status.
A timeout failure resulted in a nil error message
```
│ status: │
│ conditions: │
│ - lastTransitionTime: "2021-06-08T14:55:13Z"
│ **message: 'workflow in failure/error condition : %!w()'**
│ reason: Failed
│ status: "True"
│ type: Ready
│ - lastTransitionTime: "2021-06-08T13:48:32Z"
│ message: application group reconciliation succeeded
│ reason: Succeeded
│ status: "True"
│ type: Deploy
```

**To Reproduce**
Steps to reproduce the behavior:
Havent tried this since it was seen in the field but let me device a way to do this locally.

**Expected behavior**
A clear and concise description of what you expected to happen.
Error message should be reflected stating why the ApplicationGroup reconciliation failed.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Environment (please complete the following information):**
- Kubernetes Version [e.g. 1.21.0]
- Kubernetes Distro [e.g. AKS, GKE, etc.]
- Orkestra Version Tag
- Helm Version

**Additional context**
Add any other context about the problem here.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.