keyurusdadiya commented on issue #58470:
URL: https://github.com/apache/airflow/issues/58470#issuecomment-3774096558
Hi @bugraoz93 ,
Thank you for assigning this to me — really appreciate it!
I’ve been working on this in my own `fork` and I’ve already got **101 checks
passing** — just these last ~10 are still failing (screenshot attached for
quick reference).
Here’s where I’m at after testing locally vs. what I see in GitHub Actions:
1. **Helm chart release notes generation**
This command works perfectly on my machine `without any error`:
```
breeze release-management generate-issue-content-helm-chart
--limit-pr-count 2 --previous-release helm-chart/1.15.0 --current-release
helm-chart/1.16.0 --verbose
```
2. **Provider packages / wheel + documentation**
I ran:
```
breeze release-management prepare-provider-documentation
--include-not-ready-providers --non-interactive --answer yes --release-date
2026-01-20
```
It created/updated quite a few documentation files (provider READMEs,
changelogs, etc.).
**Quick question:** Should I commit and push all these generated doc
files to the PR branch? Or are they only supposed to be created during the
actual release process and not checked in here?
(I haven’t committed them yet — wondering if that’s causing the provider
wheel check to fail.)
3. **Kubernetes / K8s tests**
Locally this passes 100%:
```
breeze k8s run-complete-tests --upgrade --no-copy-local-sources
```
But in GitHub Actions it fails very early saying:
```
The base PROD image ghcr.io/apache/airflow/main/prod/python3.10 does not
exist locally.
Please add `--rebuild-base-image` flag or rebuild it manually with:
breeze prod-image build --python 3.10
```
The strange part: the check **“Build PROD images / Build PROD Regular
image 3.10”** finishes successfully.I belive this check run before right before
Kubernetes tests start.
**Question:** Why can’t the K8s test job find the image that was just
built? Is this a known CI thing (maybe images not shared between checks
properly)
4. **End-to-end (E2E) tests**
Locally:
```
breeze testing airflow-e2e-tests
```
→ Also passes cleanly on my local env.
So I suspect the E2E failure is just a knock-on effect from the same PROD
image / K8s issue above. As this is also followed
after `Build PROD image 3.10` check.
- Any quick fix / workaround for the “PROD image not found” error in K8s CI
(even though the build job succeeded)?
<img width="1682" height="242" alt="Image"
src="https://github.com/user-attachments/assets/93d05d3f-b026-4655-96aa-a9ef6826c1d3";
/>
<img width="1672" height="750" alt="Image"
src="https://github.com/user-attachments/assets/c0d51276-7783-4686-9cc4-96ddb24cec97";
/>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
