23.05.2019 · 3 Answers3. Show activity on this post. Restart Airflow webserver and scheduler after that. Show activity on this post. It tries to import module named kubernetes. Try that: Show activity on this post. try any of these imports. one of these got deprecated, so you might have a version that is no longer supported.
Source code for airflow.contrib.kubernetes.secret. # Licensed to the Apache Software Foundation (ASF) under one # or more contributor license agreements. See the NOTICE file # distributed with this work for additional information # regarding copyright ownership. The ASF licenses this file # to you under the Apache License, Version 2.0 (the ...
i upgraded from 1.10.3 to 1.10.4 just now but in the main page of the ui, if i click refresh button next to my dag it shows error 'Broken DAG: [x.py] No module named ...
sock to manage containers. This socket is not mounted inside Composer Airflow worker pods, and manually configuring it to do so is not recommended. Use of ...
Hi, I'm using the KubernetesExecutor into a Helm chart with your image and I noticed this error message into airflow-web container: waiting 60s... executing ...
Very new to Airflow/Python etc. but can't seem to work out what I need to do to resolve this issue.. Airflow is running on Puckel/Docker. Full error is:
Trying to create an Airflow cluster using the following resource manifest: apiVersion: airflow.apache.org/v1alpha1 kind: AirflowCluster metadata: name: pk-cluster ...
10.01.2012 · Parameters. image – Docker image you wish to launch.Defaults to hub.docker.com, but fully qualified URLS will point to custom repositories. name – name of the pod in which the task will run, will be used (plus a random suffix) to generate a pod id (DNS-1123 subdomain, containing only [a-z0-9.-]).. cmds (list[]) – entrypoint of the container.
1 Answer1. Show activity on this post. For the helm value, the template uses a loop that places the airflow.config map into double quotes ". This means any " in a value needs to be escaped for the output templated YAML to be valid. According to this github issue, the python scheduler SSL timeout may not be a problem as the watcher starts again ...