Fleet: HelmOp AppBundle: The chart is not deployed to target cluster when using Tarball source option
Setup
- Rancher version: v2.12
- Rancher UI Extensions:
- Browser type & version: Any
Describe the bug When creating a HelmOp App Bundle using a Tarball source and assigning the local cluster as a target, the user sees the warning: "There are no clusters available" on the App Bundles list page. I also noticed a message on the associated Bundle detail page: "Chart version cannot be deployed; check HelmOp status for more details: Version string empty". This occurs despite the target cluster being correctly selected in the 4th step (Target details). Tested using local and downstream clusters.
To Reproduce
- Go to Fleet > App Bundles
- Click Create App Bundle
- Select HelmOp
- In Step 2, choose Tarball as the source type
- Set Absolute URL to:
https://github.com/0xavi0/fleet-experiments/raw/refs/heads/main/zot/guestbook-0.0.1.tgz - In Step 4: select
local cluster - In Step 5: set 'Accept any certificate' to true
- Create
- Notice warning
- Go to Bundle detail page1. Notice warning
Result The chart is not deployed to the target cluster when using the Tarball source option.
Expected Result The chart is deployed to the target cluster when using the Tarball source option.
Screenshots
https://github.com/user-attachments/assets/fb504cd4-0430-49ca-8bf9-d291429c5c52
Additional context
@manno can someone from Fleet team help on this? It looks a backend issue.
@yonasberhe23 backend issue confirmed, it'll be fixed by https://github.com/rancher/fleet/commit/b59c082f46f99ecb8658313955efc52884acaed0
@yonasberhe23 the issue should have been fixed by https://github.com/rancher/fleet/pull/3795 . Moving to QA Review
Tested on latest (Rancher v2.13-d4c6dee3df3297d5233712acff0e86cba11e17bd-head / Dashboard master a820837)
Fix validated using the repro steps in the description
https://github.com/user-attachments/assets/8c225309-2257-45a0-99f1-4359d52e6c3c