You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/01/13 10:21:33 UTC

[GitHub] [airflow] p-id opened a new issue #13650: Kubernetes executor fails to create worker pod in case longer dag/task are specified

p-id opened a new issue #13650:
URL: https://github.com/apache/airflow/issues/13650


   <!--
   
   Welcome to Apache Airflow!  For a smooth issue process, try to answer the following questions.
   Don't worry if they're not all applicable; just try to include what you can :-)
   
   If you need to include code snippets or logs, please put them in fenced code
   blocks.  If they're super-long, please use the details tag like
   <details><summary>super-long log</summary> lots of stuff </details>
   
   Please delete these comment blocks before submitting the issue.
   
   -->
   
   <!--
   
   IMPORTANT!!!
   
   PLEASE CHECK "SIMILAR TO X EXISTING ISSUES" OPTION IF VISIBLE
   NEXT TO "SUBMIT NEW ISSUE" BUTTON!!!
   
   PLEASE CHECK IF THIS ISSUE HAS BEEN REPORTED PREVIOUSLY USING SEARCH!!!
   
   Please complete the next sections or the issue will be closed.
   These questions are the first thing we need to know to understand the context.
   
   -->
   
   **Apache Airflow version**: 1.10.x, 2.0
   
   
   **Kubernetes version (if you are using kubernetes)** (use `kubectl version`): 1.18.8
   
   **Environment**: Azure - AKS - ContainerD CRI-O
   
   - **Cloud provider or hardware configuration**: Azure AKS
   - **OS** (e.g. from /etc/os-release): Ubuntu 18.04.5 LTS      
   - **Kernel** (e.g. `uname -a`): 5.4.0-1031-azure
   - **Install tools**: Docker runtime  - 19.3.12
   - **Others**: ContainerD CRI-O
   
   **What happened**: Worker pod stuck in 'ContainerCreating' state - no error propagated to Airflow K8s executor for a DAG containing a longer workflow-name and task-name get specified.
   
   <!-- (please include exact error messages if you can) -->
   
   **What you expected to happen**: Worker-pod to success run OR task failure notification received due to K8s error
   
   <!-- What do you think went wrong? -->
   
   **How to reproduce it**: Run any dag/task with longer names - combined number of alphanumeric characters in dag/task name should be more than 214
   <!---
   
   As minimally and precisely as possible. Keep in mind we do not have access to your cluster or dags.
   
   If you are using kubernetes, please attempt to recreate the issue using minikube or kind.
   
   ## Install minikube/kind
   
   - Minikube https://minikube.sigs.k8s.io/docs/start/
   - Kind https://kind.sigs.k8s.io/docs/user/quick-start/
   
   If this is a UI bug, please provide a screenshot of the bug or a link to a youtube video of the bug in action
   
   You can include images using the .md style of
   ![alt text](http://url/to/img.png)
   
   To record a screencast, mac users can use QuickTime and then create an unlisted youtube video with the resulting .mov file.
   
   --->
   
   
   **Anything else we need to know**: The error seems to occur due to pod sandbox creation failure. Each K8s pod gets a specific sandbox (directory). If the pod-id generated by Airflow Kubernetes executor is more than 214 characters, K8s also add suffix/prefix to generate a specific sandbox directory (prefix the K8s namespace and suffix a 36 character UUID using '_' as delimiter). This results in the sandbox directory name to cross '255' characters which is the maximum character (bytes) limit in most of the EXT FS based filesystem. 
   
   <!--
   
   How often does this problem occur? Once? Every time etc?
   
   Any relevant logs to include? Put them here in side a detail tag:
   <details><summary>x.log</summary> lots of stuff </details>
   
   -->
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [airflow] potiuk commented on issue #13650: Kubernetes executor fails to create worker pod in case longer dag/task are specified

Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #13650:
URL: https://github.com/apache/airflow/issues/13650#issuecomment-759356754


   Closing as duplicate of #13189


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [airflow] boring-cyborg[bot] commented on issue #13650: Kubernetes executor fails to create worker pod in case longer dag/task are specified

Posted by GitBox <gi...@apache.org>.
boring-cyborg[bot] commented on issue #13650:
URL: https://github.com/apache/airflow/issues/13650#issuecomment-759352761


   Thanks for opening your first issue here! Be sure to follow the issue template!
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [airflow] potiuk closed issue #13650: Kubernetes executor fails to create worker pod in case longer dag/task are specified

Posted by GitBox <gi...@apache.org>.
potiuk closed issue #13650:
URL: https://github.com/apache/airflow/issues/13650


   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org