stackabletech / stackabletech/airflow-operator
airflow scheduler default 0 - CrashLoopBackOff
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 32
- Forks
- 6
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 13
Description
Affected Stackable version
26.7.0
Affected Apache Airflow version
3.2.2
Current and expected behavior
I'm experiencing the issue described and solved here:
Fix scheduler crashloop from KubernetesExecutor completed-pod adoption- #67850
This is caused by a bug in Airflows cncf-kubernetes provider 10.17.1 (apache-airflow-providers-cncf-kubernetes==10.17.1) wich is used in stackable v26.7.0 with airflow 3.2.2.
Possible solution
Possible solution is to update Airflows cncf-kubernetes provider to 18.0.0 or newer (apache-airflow-providers-cncf-kubernetes>=10.18.0).
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
no
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the dependency declaration for apache-airflow-providers-cncf-kubernetes in the airflow-operator repository and compare its configured version with the affected 10.17.1 release. Update it to a fixed version at least 10.18.0, then verify that the Airflow scheduler no longer enters CrashLoopBackOff.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100