<p dir="auto"><strong>Apache Airflow version</strong>: 2.1.1</p>
<p dir="auto"><strong>Kubernetes version (if you are using kubernetes)</strong> (use <code class="notranslate">kubectl version</code>):</p>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>:</li>
<li><strong>OS</strong> (e.g. from /etc/os-release):</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>): <code class="notranslate">Linux e08g09383.cloud.eu13 3.10.0-327.ali2010.rc7.alios7.x86_64 #1 SMP Thu Jun 29 21:45:21 CST 2017 x86_64 x86_64 x86_64 GNU/Linux</code></li>
<li><strong>Install tools</strong>: docker-compose</li>
<li><strong>Others</strong>:<br>
I installed the airflow via docker-compose.yaml, and my docker-compose.yaml is as attach file: <a href="https://github.com/apache/airflow/files/6915002/docker-compose.txt">docker-compose.txt</a></li>
</ul>
<p dir="auto"><strong>What happened</strong>:</p>
<p dir="auto">A task was set to be failed directly by scheduler, while all up streams were success.<br>
The task has not be run, no log info either.</p>
<p dir="auto"><strong>What you expected to happen</strong>:</p>
<p dir="auto">The task should be running</p>
<p dir="auto"><strong>How to reproduce it</strong>:<br>
It happens by chance, I can not reproduce it.</p>
<p dir="auto"><strong>Anything else we need to know</strong>:<br>
A log from scheduler:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="[2021-08-01 21:46:14,003] {scheduler_job.py:600} INFO - Executed failure callback for &lt;TaskInstance: blink_create_cluster.create_master_ecs_task 2021-08-01 13:46:09.195000+00:00 [failed]&gt; in state failed"><pre class="notranslate"><code class="notranslate">[2021-08-01 21:46:14,003] {scheduler_job.py:600} INFO - Executed failure callback for &lt;TaskInstance: blink_create_cluster.create_master_ecs_task 2021-08-01 13:46:09.195000+00:00 [failed]&gt; in state failed
</code></pre></div>
<h3 dir="auto">Apache Airflow version</h3>
<p dir="auto">2.1.4 (latest released)</p>
<h3 dir="auto">Operating System</h3>
<p dir="auto">official docker image</p>
<h3 dir="auto">Versions of Apache Airflow Providers</h3>
<p dir="auto"><em>No response</em></p>
<h3 dir="auto">Deployment</h3>
<p dir="auto">Official Apache Airflow Helm Chart</p>
<h3 dir="auto">Deployment details</h3>
<p dir="auto">using KEDA</p>
<h3 dir="auto">What happened</h3>
<p dir="auto">Somehow, downstream task ends in state 'upstream failed' even though the upstream task retried and succeeded.</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/15932138/134117913-5384a134-e060-4d05-9d48-a69b4b24c617.png"><img src="https://user-images.githubusercontent.com/15932138/134117913-5384a134-e060-4d05-9d48-a69b4b24c617.png" alt="image" style="max-width: 100%;"></a></p>
<h3 dir="auto">What you expected to happen</h3>
<p dir="auto">"upstream failed" should only happen when upstream task fails</p>
<h3 dir="auto">How to reproduce</h3>
<p dir="auto"><em>No response</em></p>
<h3 dir="auto">Anything else</h3>
<p dir="auto"><em>No response</em></p>
<h3 dir="auto">Are you willing to submit PR?</h3>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Yes I am willing to submit a PR!</li>
</ul>
<p dir="auto">But I have no ideas about cause here.</p>
<h3 dir="auto">Code of Conduct</h3>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I agree to follow this project's <a href="https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md">Code of Conduct</a></li>
</ul>