mjpieters opened a new issue #12289:
URL: https://github.com/apache/airflow/issues/12289


   **Apache Airflow version**: 2.0.0b2
   
   **Environment**:
   - **Others**: No K8S
   
   **What happened**:
   
   In the The *Logs* and *All Instances* buttons in the task model in the web 
UI are inoperative when _not_ using Kubernetes.
   
   **What you expected to happen**:
   
   The buttons to have working links. 
   
   The `dag.html` `updateModalUrls()` function [assumes that 
`buttons.rendered_k8s` is 
set](https://github.com/apache/airflow/blob/7d5d334857114903783390333e23e07bc9df2e2e/airflow/www/templates/airflow/dag.html#L428-L434),
 which is not the case when not using K8S.
   
   This then results in an error and the buttons initialised after this point 
are not wired up:
   
   ```js
   18:28:17.990 Uncaught TypeError: elm is undefined
       updateButtonUrl http://158.101.169.4:8080/tree?dag_id=full_pipeline:1595
       updateModalUrls http://158.101.169.4:8080/tree?dag_id=full_pipeline:1616
       call_modal http://158.101.169.4:8080/tree?dag_id=full_pipeline:1665
       update http://158.101.169.4:8080/tree?dag_id=full_pipeline:1427
       $/< http://158.101.169.4:8080/static/dist/d3.min.js:1
       i http://158.101.169.4:8080/static/dist/d3.min.js:1
       each http://158.101.169.4:8080/static/dist/d3.min.js:3
       Y http://158.101.169.4:8080/static/dist/d3.min.js:1
       each http://158.101.169.4:8080/static/dist/d3.min.js:3
       on http://158.101.169.4:8080/static/dist/d3.min.js:3
       update http://158.101.169.4:8080/tree?dag_id=full_pipeline:1420
       <anonymous> http://158.101.169.4:8080/tree?dag_id=full_pipeline:1339
   tree:1595:7
   ```
   
   The call needs to be protected by a `k8s_or_k8scelery_executor` check.


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