jason810496 commented on PR #47433:
URL: https://github.com/apache/airflow/pull/47433#issuecomment-2708289346

   I ran the Kubernetes tests locally yesterday, and they all passed. However, 
after rebasing today, they consistently fail.  
   It seems that triggering a `dagRun` results in a 404 error:  
   
https://github.com/apache/airflow/blob/2ea7aed755006cfff3dedd30b5654e8e2534e197/kubernetes_tests/test_base.py#L270
  
   ```
   self = <requests.adapters.HTTPAdapter object at 0x119d835b0>, request = 
<PreparedRequest [POST]>, stream = False, timeout = Timeout(connect=None, 
read=None, total=None), verify = True, cert = None, proxies = OrderedDict()
   
   # ...
       
           except MaxRetryError as e:
               if isinstance(e.reason, ConnectTimeoutError):
                   # TODO: Remove this in 3.0.0: see #2811
                   if not isinstance(e.reason, NewConnectionError):
                       raise ConnectTimeout(e, request=request)
       
               if isinstance(e.reason, ResponseError):
   >               raise RetryError(e, request=request)
   E               requests.exceptions.RetryError: 
HTTPConnectionPool(host='localhost', port=14476): Max retries exceeded with 
url: /public/dags/example_kubernetes_executor/dagRuns (Caused by 
ResponseError('too many 404 error responses'))
   ```
   
   Tracing the issue on the API side, it looks like the DAG must be **active** 
to be triggered:  
   
https://github.com/apache/airflow/blob/2ea7aed755006cfff3dedd30b5654e8e2534e197/airflow/api_fastapi/core_api/routes/public/dag_run.py#L349-L352
  
   
   However, in the **patch DAG** endpoint, only the `is_paused` field can be 
modified, while the `is_active` field cannot be changed:  
   
https://github.com/apache/airflow/blob/2ea7aed755006cfff3dedd30b5654e8e2534e197/airflow/api_fastapi/core_api/routes/public/dags.py#L218-L228


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