[jira] [Commented] (AIRFLOW-2665) No BASH will cause the dag to fail

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591387#comment-16591387 ] 

ASF GitHub Bot commented on AIRFLOW-2665:
-----------------------------------------

barrachri opened a new pull request #3799: [AIRFLOW-2665] Use shlex to split args and remove shell true
URL: https://github.com/apache/incubator-airflow/pull/3799
 
 
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [ ] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-XXX
     - In case you are fixing a typo in the documentation you can prepend your commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
   
   ### Description
   
   - [ ] Here are some details about my PR, including screenshots of any UI changes:
   
   ### Tests
   
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes how to use it.
     - When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.
   
   ### Code Quality
   
   - [ ] Passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> No BASH will cause the dag to fail
> ----------------------------------
>
>                 Key: AIRFLOW-2665
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2665
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Christian Barra
>            Priority: Major
>              Labels: easy-fix
>
> If you are a running airflow in a system where bash is not available the dags will fail, with no logs inside the UI (you have to scroll through the local logs).
> How to replicate this? just use an alpine based image:
> ```
> [2018-06-22 21:05:20,659] \{jobs.py:1386} INFO - Processing DAG_1
>  [2018-06-22 21:05:20,667] \{local_executor.py:43} INFO - LocalWorker running airflow run DAG_1 stackoverflow 2018-06-22T21:05:19.384402 --local -sd /usr/local/airflow/dags/my_dag.py
>  /bin/sh: exec: line 1: bash: not found
>  [2018-06-22 21:05:20,671] \{local_executor.py:50} ERROR - Failed to execute task Command 'exec bash -c 'airflow run DAG_1 my_task 2018-06-22T21:05:19.384402 --local -sd /usr/local/airflow/dags/my_dag.py'' returned non-zero exit status 127..
>  /bin/sh: exec: line 1: bash: not found
> ```



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)