trowdan opened a new issue #14727:
URL: https://github.com/apache/airflow/issues/14727


   **Apache Airflow version**: 2.0.0
   
   
   **Kubernetes version** : 1.19.2
   
   **Environment**:
   
   - **Cloud provider** : Openshift
   
   **What happened**:
   
   Once a task in a task group is queued the scheduler throws exeptions like 
the following one:
   _Note: <dag_name>, <task_group_1>, <task_group_2>, <task_id> are 
**placeholders**_
   ```
   [2021-03-11 16:52:48,409] {kubernetes_executor.py:579} WARNING - 
ApiException when attempting to run task, re-queueing. Message: Pod 
"<dag_name><task_group_1><task_group_2><task_id>-5cecda4b56a34c4ea061b1746d1879bb"
 is invalid: metadata.labels: Invalid value: 
"<task_group_1>.<task_group_2>.<task_id>": must be no more than 63 characters
   
   [2021-03-11 16:52:48,410] {kubernetes_executor.py:277} INFO - Kubernetes job 
is (TaskInstanceKey(dag_id='<dag_name>', 
task_id='<task_group_1>.<task_group_2>.<task_id>', 
execution_date=datetime.datetime(2021, 3, 11, 16, 46, 42, 990210, 
tzinfo=Timezone('UTC')), try_number=1), ['airflow', 'tasks', 'run', 
'<dag_name>', '<task_group_1>.<task_group_2>.<task_id>', 
'2021-03-11T16:46:42.990210+00:00', '--local', '--pool', 'default_pool', 
'--subdir', '/opt/airflow/dags/<dag_name>'], None, None)
   
   [2021-03-11 16:52:48,432] {pod_launcher.py:86} ERROR - Exception when 
attempting to create Namespaced Pod: {
   ```
   
   **What you expected to happen**:
   Tasks in task group are scheduled as expected
   
   **How to reproduce it**:
   Create a dag with the following structure:
   
   * Task_group_1
      * Task_group_2
         * Task_id
   
   make the sum of the 3 labels > 63
   
   
   **Anything else we need to know**:
   It seems releated to this one https://github.com/apache/airflow/pull/4636
   


----------------------------------------------------------------
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:
[email protected]


Reply via email to