Dan MacTough created AIRFLOW-4760:
-------------------------------------
Summary: Packaged DAGs disappear from the DagBag
Key: AIRFLOW-4760
URL: https://issues.apache.org/jira/browse/AIRFLOW-4760
Project: Apache Airflow
Issue Type: Bug
Components: models
Affects Versions: 1.10.3, 1.10.2, 1.10.1, 1.10.4, 2.0.0
Reporter: Dan MacTough
Assignee: Dan MacTough
Attachments: 2019-06-07-ghosting-before.gif
AIRFLOW-2900 introduced a change that broke Airflow whenever it tries to
reprocess a packaged DAG. Since that change, the {{fileloc}} column in the
database for packaged DAGs isn't an actual filepath. It looks something like:
{{/usr/local/airflow/dags/package.zip/my_dag.py}} -- *notice that the path to
the DAG inside the zip is appended to the zip file's path*. Then, when the
{{DagBag#process_file}} method tries to load that filepath, it bails because
that filepath is invalid.
Steps to reproduce:
# Add a packaged DAG to your DAGS_FOLDER
# From the main /admin UI, click on the DAG to open it's detail view
# Click the "Refresh" button
What should happen:
The detail view should refresh and display a "flash" message saying that the
DAG is "fresh as a daisy."
What actually happens:
The app redirects to the main /admin UI and displays a "flash" error message in
addition to the "fresh as a daisy" message.
See animated GIF, attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
