Addon-Operation - WFR Status Always Shows Failed
- Dominant language
- Go
- Stars
- 126
- Forks
- 66
- Avg merge
- 1h 40m
- Merged PRs (30d)
- 1
Description
**Describe the bug**
When deploying addons with the addon-operation workflow step, the WorkflowRun always shows status failed despite the addon successfully installing.
**To Reproduce**
Apply this WorkflowRun:
```
apiVersion: core.oam.dev/v1alpha1
kind: WorkflowRun
metadata:
name: test-addon-operation
namespace: default
spec:
context:
readConfig: true
mode:
workflowSpec:
steps:
- name: Enable Prism
type: addon-operation
properties:
addonName: vela-prism
image: "oamdev/vela-cli:v1.10.3"
```
Check the WFR status which will be in failed status:
```
kubectl get workflowruns.core.oam.dev test-addon-operation
```
However, the addon status will be enabled (or will be):
```
vela addon status vela-prism
```
**Expected behavior**
The WFR should correctly reflect that the addon installed successfully.
**Screenshots**
**KubeVela Version**
CLI Version: 1.10.3
Core Version: 1.10.3
**Cluster information**
Client Version: v1.31.2
**Additional context**
I'm using an updated image in the addon-operation properties due to the separate issue described in https://github.com/kubevela/workflow/issues/208
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the issue with the provided WorkflowRun manifest, then trace the addon-operation workflow step and its WorkflowRun status handling. Compare the reported status with `vela addon status vela-prism`; done means a successfully installed addon produces a successful WorkflowRun status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100