airflow: Quickstart Helm Chart fails post-install

Apache Airflow version: 2.0.2

Kubernetes version (if you are using kubernetes) (use kubectl version): 1.19

Environment:

  • Cloud provider or hardware configuration: Running kind locally
  • OS (e.g. from /etc/os-release): macOS
  • Kernel (e.g. uname -a): Darwin MacBook-Pro 19.6.0 Darwin Kernel Version 19.6.0: Mon Apr 12 20:57:45 PDT 2021; root:xnu-6153.141.28.1~1/RELEASE_X86_64 x86_64
  • Install tools: brew
  • Others:

What happened:

Helm chart does not successfully deploy to a kind cluster despite following the Quick Start. Repeatedly tried multiple times and the flower, postgres, redis and statsd services run fine but it fails at the run-airflow-migrations service with a CrashLoopBackoff:

  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  5m19s                  default-scheduler  Successfully assigned airflow/airflow-run-airflow-migrations-c9pph to kind-control-plane
  Normal   Pulled     2m43s (x5 over 5m17s)  kubelet            Container image "apache/airflow:2.0.2" already present on machine
  Normal   Created    2m43s (x5 over 5m17s)  kubelet            Created container run-airflow-migrations
  Normal   Started    2m43s (x5 over 5m17s)  kubelet            Started container run-airflow-migrations
  Warning  BackOff    9s (x18 over 4m25s)    kubelet            Back-off restarting failed container

What you expected to happen:

Successful Helm deployment.

How to reproduce it:

  1. Created a kind cluster: kind create cluster --image kindest/node:v1.18.15
  2. Added Helm chart repo: helm repo add apache-airflow https://airflow.apache.org
  3. Created kube namespace: kubectl create namespace airflow
  4. Installed chart: helm install airflow apache-airflow/airflow --namespace airflow --debug
install.go:173: [debug] Original chart version: ""
install.go:190: [debug] CHART PATH: /Users/stephaniesamson/Library/Caches/helm/repository/airflow-1.0.0.tgz

client.go:282: [debug] Starting delete for "airflow-broker-url" Secret
client.go:122: [debug] creating 1 resource(s)
client.go:282: [debug] Starting delete for "airflow-fernet-key" Secret
client.go:122: [debug] creating 1 resource(s)
client.go:282: [debug] Starting delete for "airflow-redis-password" Secret
client.go:122: [debug] creating 1 resource(s)
client.go:122: [debug] creating 30 resource(s)
client.go:282: [debug] Starting delete for "airflow-run-airflow-migrations" Job
client.go:122: [debug] creating 1 resource(s)
client.go:491: [debug] Watching for changes to Job airflow-run-airflow-migrations with timeout of 5m0s
client.go:519: [debug] Add/Modify event for airflow-run-airflow-migrations: ADDED
client.go:558: [debug] airflow-run-airflow-migrations: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:519: [debug] Add/Modify event for airflow-run-airflow-migrations: MODIFIED
client.go:558: [debug] airflow-run-airflow-migrations: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
Error: failed post-install: timed out waiting for the condition
helm.go:81: [debug] failed post-install: timed out waiting for the condition

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 4
  • Comments: 67 (28 by maintainers)

Most upvoted comments

LOL,

Politeness is not necessary. We just want useful answers. This thread is a testament to the lack of the latter by far more people than just myself. So, feel free to blame me as the user/customer.

Best of luck to you and this project.

Regards,

Alex


“The Only Way To Get The Best Of An Argument Is To Avoid It. An argument is 90% emotion and 10% nonsense. A mature professional avoids arguments.” – Dale Carnegie “How to Win Friends and Influence People”

On Mon, Apr 25, 2022 at 11:23 AM Jarek Potiuk @.***> wrote:

LOL, I have never gotten a polite (or useful) response from this project. I guess it’s part of your charm. 😁

I really love when people make such precise statement. I looked for your questions and well, I could not find any. There has never been a polite nor useful answer because you … never asked any question. Unless of course my search is wrong and you will point out to those impolite and nonuseful answers to questions I could not find.

I think if you want polite answers it’s good to be factual and read the discussion before you ask a question when you were explicity asked in a previous post to not to do it and ask your question differently - in the way that might be of help to both yourself and those who try to provide help to people in their free time for the software they paid 0 USD for. Asking questions like that when you are asked not to do so is well, impolite at the very least.

— Reply to this email directly, view it on GitHub https://github.com/apache/airflow/issues/16176#issuecomment-1108718224, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATW2DP3VB45JVPA7VFJ7N7DVG22H3ANCNFSM45ZZL77A . You are receiving this because you were mentioned.Message ID: @.***>

Hi everyone,

I have run into the same issue on a fresh microk8s cluster. After running the following command: microk8s.helm3 install airflow apache-airflow/airflow --namespace airflow --wait=false Error: failed post-install: timed out waiting for the condition

I have tried deleting the namespace and updating the repo several times.

Anyone running into the same issues?

It’s solved, I was inside my companies vpn, so I was unable to pull the images from docker. I pulled and pushed the images to my remote repo, and it started working. 😃

LOL,

I have never gotten a polite (or useful) response from this project. I guess it’s part of your charm. 😁

I simply used bash scripts and that worked like a charm (though obviously less than ideal for sustainment and scaling). It is really disappointing that following the instructions did not work. I am willing to accept user error as the cause, but at least I know I am not alone.

Regards,

Alex


“The Only Way To Get The Best Of An Argument Is To Avoid It. An argument is 90% emotion and 10% nonsense. A mature professional avoids arguments.” – Dale Carnegie “How to Win Friends and Influence People”

On Tue, Apr 19, 2022 at 2:06 AM Jarek Potiuk @.***> wrote:

Exactly the same issue

I think you missed the note above @Alejandro13Rob https://github.com/Alejandro13Rob @alexperry-shifu https://github.com/alexperry-shifu . So let me just repeat it again.

Please open a detailed issue about this with more details (logs and describing what you experience). It might likely be a different issue. The comment “I have the same issue” on a closed issue does not help in any meaningful way in diagnosing the issue.

Honestly I am not sure what is the goal of commenting “I have the same issue” without providing this extra information.

This is just well, completely useless. If your goal is to get some help, you must provide more information. I am not sure if you have other goals, but certainly it does not help anyone (including your case), It’s quite mind-boggling why would anyone do it (especially if there was an earlier comment asking to do it differently - in the way that it can be helpful for both - maintainers and yourself, rather than in the way that has 0 chances of helping anyone.

— Reply to this email directly, view it on GitHub https://github.com/apache/airflow/issues/16176#issuecomment-1102127786, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATW2DPZYRSZHI3HD2NRGN7DVFZEMZANCNFSM45ZZL77A . You are receiving this because you were mentioned.Message ID: @.***>

Exactly the same issue

I think you missed the note above @Alejandro13Rob @alexperry-shifu . So let me just repeat it again.

Please open a detailed issue about this with more details (logs and describing what you experience). It might likely be a different issue. The comment “I have the same issue” on a closed issue does not help in any meaningful way in diagnosing the issue.

Honestly I am not sure what is the goal of commenting “I have the same issue” without providing this extra information.

This is just well, completely useless. If your goal is to get some help, you must provide more information. I am not sure if you have other goals, but certainly it does not help anyone (including your case), It’s quite mind-boggling why would anyone do it (especially if there was an earlier comment asking to do it differently - in the way that it can be helpful for both - maintainers and yourself, rather than in the way that has 0 chances of helping anyone.

Up, I am facing the same issue. Could not find a workaround. I used 10m timeout but it did not work

We really need more details - values, configurtions, detaile logs from the “wait-for-migrations” jobs etc

I got the same issue, but installing older version worked for me helm install airflow apache-airflow/airflow --namespace airflow --version 1.0.0 Probably something is wrong with the current latest chart version

@ephraimbuddy thanks that worked!

@stephsamson can you delete the namespace and recreate it. Then run helm repo update before install?