kaxil commented on PR #49433:
URL: https://github.com/apache/airflow/pull/49433#issuecomment-2826763168

   That said, the error reported in the GH issue around validation, does not 
need to happen when the task is already in the KPO pod i.e. there is no needed 
to load or create a Executor:
   
   ```
   │ Traceback (most recent call last):                                         
                                                                                
                                                                                
                                  │
   │   File 
"/home/airflow/.local/lib/python3.12/site-packages/airflow/models/dag.py", line 
852, in validate_executor_field                                                 
                                                                                
                      │
   │     ExecutorLoader.lookup_executor_name_by_str(task.executor)              
                                                                                
                                                                                
                                  │
   │   File 
"/home/airflow/.local/lib/python3.12/site-packages/airflow/executors/executor_loader.py",
 line 215, in lookup_executor_name_by_str                                       
                                                                                
             │
   │     raise UnknownExecutorException(f"Unknown executor being loaded: 
{executor_name_str}")                                                           
                                                                                
                                         │
   │ airflow.exceptions.UnknownExecutorException: Unknown executor being 
loaded: KubernetesExecutor
   ```


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

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to