Tim Blazina created AIRFLOW-6506:
------------------------------------
Summary: KubernetesPodOperator defaulting do_xcom_push to True
after 1.10.7 release
Key: AIRFLOW-6506
URL: https://issues.apache.org/jira/browse/AIRFLOW-6506
Project: Apache Airflow
Issue Type: Bug
Components: executor-kubernetes, xcom
Affects Versions: 1.10.7
Reporter: Tim Blazina
Assignee: Daniel Imberman
{color:#1d1c1d}After updating to 1.10.7, I am getting
{color}
[2019-12-27 11:37:42,220] \{{logging_mixin.py:112}} INFO - [2019-12-27
11:37:42,219] \{{pod_launcher.py:217}} INFO - Running command... cat
/airflow/xcom/return.json
[2019-12-27 11:37:42,286] \{{logging_mixin.py:112}} INFO - [2019-12-27
11:37:42,286] \{{pod_launcher.py:224}} INFO - cat: can't open
'/airflow/xcom/return.json': No such file or directory`
for tasks run with the KubernetesPodOperator. {color:#1d1c1d}I see that there
is a {color}{{do_xcom_push}}{color:#1d1c1d} attribute for the
{color}{{KubernetesPodOperator}}{color:#1d1c1d} and if I set this to
{color}{{False}}{color:#1d1c1d} I do not get this error{color}.
When discussing issue in slack - [~dimberman] rightly pointed to -[
https://github.com/apache/airflow/commit/d1664d2e507024489c565808ebe2e5b48a1797ef#diff-f9bc463ffc2cc8fd3967968549c5639fR122|https://github.com/apache/airflow/commit/d1664d2e507024489c565808ebe2e5b48a1797ef#diff-f9bc463ffc2cc8fd3967968549c5639fR122]
- as the culprit and [~potiuk] commented that "{color:#1d1c1d}There was no
UPDATING.md note with it, so I missed that there is a breaking change for
do_xcom_push while cherry-picking{color}"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
